On 2017-02-04 03:57, Philip Guenther wrote:
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
Remaking filesystems from ground up is an arduous task, and putting
yourself at unnecessary risk of needing to do it is stupid -
So that sounds like an excellent reason to never ever mount filesystems
with any important info on them in "async" but only as "softdep" and
"sync"!
In particular for SSD:s.
"softdep" is 1) essentially as safe as "sync" though and 2) should come
with some performance benefits on both SSD:s and magnet disks, right?
