156 ;;Quote: failure of one or two consecutive sectors should only affect the corresponding file; the file name table survives single sector errors

156 ;;Quote: a file system should be high performance, robust against some software errors, and use available hardware

156 ;;Quote: file recovery from single sector errors should be fast; can not scan the entire disk

156 ;;Quote: each file has a leader page that contains file name information, unique id, and run table header

157 ;;Quote: write changes of the file name table and leader pages to a redo log; recovery in about two seconds; log entry format

157 ;;Quote: Cedar uses group commit to log multiple updates together; done every half second

157 ;;Quote: Cedar's file name table is mirrored to different locations; both copies checked on reads; logging allows delayed writes

158 ;;Quote: Cedar divides its circular log file into thirds; on entering a new third, Cedar flushes modified data not logged elsewhere; recorded in header

159 ;;Quote: Cedar uses a free page bit map; reconstruct if necessary; shadow bitmap for uncommitted file deletes

159 ;;Quote: Cedar partitions the disk into big and small file areas to curtail fragmentation; the areas are hints

159 ;;Quote: leader pages for files not as robust as headers and sector labels; bugs no longer detected when they occur; can damage file system