-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/22/2012 05:58 AM, grarpamp wrote: > Been looking for a distributed filesystem with no luck, any ideas? > > Distributed meaning that there is no single central access point. > So the concept of mounting might mean amongst the roving set able > to service it, or some underlying graph of it, something like: > > mount -t dht dht://<seed_node> /dist1 > > > Users add their free block devices to the global backing store which > was initialized with certain ZFS-like integrity and redundancy > guarantees. > > Files would never vanish unless there are no longer enough blocks > in the backing store to meet the init time guarantees. > > Users could either copy their hierarchies into the space, or attach > them into the space for continued local maintenance. > > The one time init setting of a space could include whether pki > recognized root users could maintain the overall hierarchy. Uid's > might be an insertion node id. > > There may need to be voting authority on file/tree expiry if under > space pressure, perhaps bitcoin-like, with the metrics established > at init time. > > Users could add their block devices to whatever pool had the metrics > they like. > > Anononymity and crypto would provide incentive to donate resources > since unlike say bittorrent, no legal fear means no hit and run > required. > > > I don't really know what it might look like. Just that it needs > sha2/3 integrity, redundancy, and file lifetime guarantees. It needs > to be global, anonymous, and be a usable file system. And somehow > deal with abusive fill such as dd if=/dev/zero of=zero, which implies > some kind of moderated hierarchies appointed by the initializing > entity. > > AFS is nice that users can bolt their filespace into the tree, and > it has filesystem semantics. > > ZFS/BTRFS is nice due to their sha256 integrity, raidz redundancy > and simple backing block device ideas. > > FreeNet/GnuNet/BitTorrent and all other 'filesharing' protocols are > no good because there is no guarantee that files will not vanish. > And they have no filesystem semantics, only push/fetch. > > RedHat GFS / DragonFly HAMMER are interesting as a distributed > filesystem in which real work can be done on live files. > > Tahoe-LAFS is nice due to adding in block devices, but no good > because of the central access point. Perhaps that could be distributed? > > Phantom/I2P/Tor could be used as the backend IP transport. > > http://en.wikipedia.org/wiki/List_of_file_systems#Distributed_parallel_fault-tolerant_file_systems > > > The only thing that makes it worth while is that a lot of people > have free space, want to give an get data, safely, and don't want > to see their work in populating it wasted... so it can't go away.
I don't quite understand. The system must be [anonymous in the sense that the uploader cannot be identified] && [have moderation system based on something other than the blocks popularity like in GnuNet/Freenet*]. The system must be [using limited amount of disk space given by its users] and [provide infinite storage guarantee when moderation doesn't apply]. I think that the reason why you can't find this filesystem is akin to the reason why all-powerful, all-knowing, and all-good god has not been spotted yet. *Freenet has gone so far as to disable the already implemented feature which gave people the key to announce to others before the file was completely inserted. That is because if you can associate different blocks of the file to the same file you open yourself up to quite a few possible attacks... and moderation based on the entire file will by definition have to associate different parts of that file with each other. - -- http://freedom.libsyn.com/ Echo of Freedom, Radical Podcast "None of us are free until all of us are free." ~ Mihail Bakunin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPa3WsAAoJENW9VI+wmYasxwIH/3UMYkNVwZzzkYb6KGUa5HRk iW4gl2jktniSmg6ov7DCZjJ27SkDLITZ5HmO6dHRXe8hXBy+WpJ/lwmZFdcyvXKH CBSicCQ9FGX4WyLRw4GwPfiOVVIOZFJKQwaTzASocpH32lAzF6dnEm5o8krH5OVM 6sC5TyJBG4WjSO4vYkJsi10BBW9tzKwjLRLhUVRKAoyQilbt7Bl8yeGF4Kv7a23E VsHHNUMKyWmxGaut1W7nL7g35bzZU/N4RzEHeSjc3FvdjSObH0psH3+XKxIcSb03 RPObJxy0f4GGLOsyj3LoqfeOwOVRjRNqNc2+/HH8lTXWBXTLMOPo6kwytStyFqg= =eVHu -----END PGP SIGNATURE----- _______________________________________________ p2p-hackers mailing list p2p-hackers@lists.zooko.com http://lists.zooko.com/mailman/listinfo/p2p-hackers
