I work on a project to automatically (by dynamically running the
system) find crash recovery errors in storage systems and we are
beginning to do some preliminary checking of FreeBSD. We found an
"error" where on power failure the disk can get corrupted even after
an operation has returned successfully on a synchronous mount. Fsck
running with the -p option cannot fix this error, while running it
without, does happen to fix it (in this particular test case).
However, the fsck manfile says the following:
"The kernel takes care that only a restricted class of innocuous file
tem inconsistencies can happen unless hardware or software
intervene. These are limited to the following:
Link counts in inodes too large
Missing blocks in the free map
Blocks in the free map also in files
Counts in the super-block wrong
These are the only inconsistencies that fsck_ffs with the -p
correct; if it encounters other inconsistencies, it exits with
mal return status and an automatic reboot will then fail. For
rected inconsistency one or more lines will be printed
file system on which the correction will take place, and the
the correction. After successfully correcting a file system,
will print the number of files on that file system, the number
and free blocks, and the percentage of fragmentation."
Would you consider it an error if the -p option does not fix
inconsistencies caused by a simple power failure, without any
hardware or software corruption?
I have two example ufs2 images of such errors that you can download.
Thank you very much for your help,
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"