UFS not handling errors correctly
peter.schuller at infidyne.com
Sun Sep 9 13:09:35 PDT 2007
> bg fsck cannot fix arbitrary filesystem corruption. Nor is it intended to.
But is not the proposed problem that UFS caused the corruption to
Given that updates are already done in such a way as to cause
predictable inconsistency in the event of a crash, should not
appropriate course of action in a case such as this be to panic,
unmount the fs, rollback and error out, or otherwise abort the
operation in a way the filesystem can be fsck:ed and re-mounted
(assuming the device is alive), rather than cause corruption?
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller at infidyne.com>'
Key retrieval: Send an E-Mail to getpgpkey at scode.org
E-Mail: peter.schuller at infidyne.com Web: http://www.scode.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20070909/b85322bd/attachment.pgp
More information about the freebsd-fs