- distributed read-write locking at the byte granularity;
- user visible distributed transactions with isolation and roll-back;
- capability based authentication;
- files implemented as B-trees;
- distributed garbage collection of unreferenced objects;
- atomicity through COW (aka shadow writes, aka wandering logs);
- intent logging of file system updates (hello, ZFS);
- storage failure resilience methods, similar to ones in TileFS;
- directories implemented as separate service, using the same interface as usual clients.
[0] James G. Mitchell, Jeremy Dion A comparison of two network-based file servers
[1] Jeremy Dion The Cambridge File Server
>Funny enough, one of them is even >named CFS.
ReplyDeleteThis would not be the first time.
http://www-verimag.imag.fr/SYNCHRONE/index.php?page=lustre-story/history