On Wed, October 19, 2011 08:15, Pawel Jakub Dawidek wrote:
> Fsck can only fix known file system inconsistencies in file system
> structures. Because there is no atomicity of operations in UFS and other
> file systems it is possible that when you remove a file, your system can
> crash between removing directory entry and freeing inode or blocks.
> This is expected with UFS, that's why there is fsck to verify that no
> such thing happend.
Slightly OT, but this non-atomic delay between meta-data updates and
writes to the disk is exploited by "soft updates" with FreeBSD's UFS:
It may be of some interest to the file system geeks on the list.
zfs-discuss mailing list