On Fri, 3 Feb 2017, Tinker wrote: > After rebooting the machine (now in ordinary softdep mode, and fsck did > its job), I tried to do "rm -rf /home/lost+found", and got "ffs_blkfree: > freeing free block". ... > I'm not so freaked out by this error as indeed my FS must have been in a > badly inconsistent state, however, nonetheless I guess this is a bug.
Unfortunately, there are possible corruptions which fsck cannot repair or does not detect. This includes some failures 'below' the filesystem, as well as kernel bugs, random scribling to the device, etc. When something like that happens, then way to get back to a totally consistent filesystem is, unfortunately: backup, newfs, restore. The bug to fix is whatever go the system into this state...which basically requires analysis at the time of the original corruption. Filesystems are hard, let's go shopping! Philip
