[phaz0n]

https://en.wikipedia.org/wiki/InterPlane...ile_System

This seems to do a lot of what you are talking about.
Keep in mind that in distributed systems are much more complicated than their centralized counterparts. I am sure you will have no problem implementing the filesystem, but there is the entire p2p networking stack to worry about as well.
If the purpose is simply to store your own encrypted files securely, there is not enough incentive for other nodes to bear the cost of storing your encrypted data, which is useless to them. At this point you might as well just devise a centralized FS built for data redundancy and use of encryption.
Where distributed file systems really shine is not as a vault for selfish encrypted data storage but rather a cryptographically authenticated public lookup table of content, wherein each file is usually addressed by its hash. This allows nodes that share a file(s) of interest to efficiently store parts of the content, and share said parts among themselves.

In other words, there's no point distributing data you want to keep to yourself, especially since there is nothing to gain from someone storing your encrypted data for you. If you want the redundancy/fault tolerance then just write a normal FS for that IMHO.