Ensuring Volume Consistency after Server Crashes

Coda servers ensure file system consistency after a crash by running fsck(8), recovering RVM, and running the Coda salvager. The fsck used here a CMU has been modified so that it does not require every inode to be referenced, as Coda accesses inode directly.


The vanilla fsck must not be used on a Coda file system partition as the Coda files will be thrown away.

After the server machine is booted, the codasrv process starts and RVM recovers the servers committed state. The Coda salvager then reconciles the results from fsck and the salvager.