July 1, 2009 at 05:40Secure Distributed File System
In general, the idea appeared a long time ago. Maybe a year ago I came across a mention of such a development, but I don’t know how to look now. Perhaps my idea is not new and banal. So ...
Torrent Secure Distributed File System. Sounds, of course, pathetic.
Essence:
1. The file system is a network distributed file system, with redundant duplication, encryption, block-by-block splitting of each file across multiple network nodes. Roughly speaking, network RAID, where a separate physical disk of a volume group is the space allocated by an individual user. User space can be either shared by a user group or private.
2. For FS to work, you need constant access to the Internet, and the higher the connection speed, the better. It is possible to impose a speed limit on network access. You do not want to wait 2 hours for the launch of your favorite program? :). You can build a file system on the basis of a local network, then the speed issue is solved more easily. But it is rarely possible to find such large networks that can ensure the constant availability of all files.
3. Have 1-2 -... n trackers to coordinate users.
4. Each user allocates a place for data storage, for example from 1GB to infinity. In this case, you can impose a limit on the disk capacity for the user, taking into account the allocated volume for the network storage and the availability of free space in a distributed network.
5. Undoubtedly, in a distributed network there should be at least 15-20 people (ideally we are talking about thousands), for sufficient file splitting, say into 5 parts (a part does not mean a linear copy of 1 \ 5 file, as well as when transmitting in torrents 20% of the data is in shuffle form, with each part being duplicated in at least 3-4 storage nodes
6. It is possible to allocate a cache on the user's disk, the 2nd section which stores the last whole received files from the network. at the start of the FS communication session, the key is stored in the opera memory until the end of the session. Accordingly, in a critical situation (session break \ reset \ equipment removal) access to the cached data will be closed forever.
Do you think this system has the right to life?
PS Of course, users can use this development for any purpose, including for storing illegal content. But, first of all, I described a system that allows you to have your files always online, and to be sure that the storage is available only for you alone (in comparison with services providing network drives, where the guarantee that your files are visible only to you once viewed html page with some agreement)
Essence:
1. The file system is a network distributed file system, with redundant duplication, encryption, block-by-block splitting of each file across multiple network nodes. Roughly speaking, network RAID, where a separate physical disk of a volume group is the space allocated by an individual user. User space can be either shared by a user group or private.
2. For FS to work, you need constant access to the Internet, and the higher the connection speed, the better. It is possible to impose a speed limit on network access. You do not want to wait 2 hours for the launch of your favorite program? :). You can build a file system on the basis of a local network, then the speed issue is solved more easily. But it is rarely possible to find such large networks that can ensure the constant availability of all files.
3. Have 1-2 -... n trackers to coordinate users.
4. Each user allocates a place for data storage, for example from 1GB to infinity. In this case, you can impose a limit on the disk capacity for the user, taking into account the allocated volume for the network storage and the availability of free space in a distributed network.
5. Undoubtedly, in a distributed network there should be at least 15-20 people (ideally we are talking about thousands), for sufficient file splitting, say into 5 parts (a part does not mean a linear copy of 1 \ 5 file, as well as when transmitting in torrents 20% of the data is in shuffle form, with each part being duplicated in at least 3-4 storage nodes
6. It is possible to allocate a cache on the user's disk, the 2nd section which stores the last whole received files from the network. at the start of the FS communication session, the key is stored in the opera memory until the end of the session. Accordingly, in a critical situation (session break \ reset \ equipment removal) access to the cached data will be closed forever.
Do you think this system has the right to life?
PS Of course, users can use this development for any purpose, including for storing illegal content. But, first of all, I described a system that allows you to have your files always online, and to be sure that the storage is available only for you alone (in comparison with services providing network drives, where the guarantee that your files are visible only to you once viewed html page with some agreement)