2009/1/18 Duncan <[email protected]>: > "P.V.Anthony" <[email protected]> posted > [email protected], excerpted below, on Sun, 18 Jan 2009 > 02:04:33 +0800: > > FWIW, I too have the fsck service deactivated here, as you do, by setting > the fsck order column in fstab to 0. On reiserfs, which is what I run > here for pretty much everything, it's not really needed anyway, since > reiserfs automatically does pretty much everything it could do in a > normal fsck at mount in any case, and if it's beyond that, it's time for > --rebuild-tree. But I've not had to run that in /ages/, I think since > the kernel got and activated by default data=ordered for reiserfs, and > likely since I've been on Gentoo as well. (IDR which came first, > reiserfs data=ordered or my switch to Gentoo, but I sure do remember > looking forward to each of them! =:^) But, while that eliminates the > (unnecessary for reiserfs) fsck time, because reiserfs can take a bit to > replay the journal if the system crashed or the filesystems were > otherwise not unmounted properly, you may end up with the same problem > under those conditions. > i'd like to know if there's something particular to be aware of disabling fsck on boot with reiserfs and if there are some other things than removing the service from boot runlevel to be aware of. i'm using reiserfs v3.6 revision, r5 hash with ordered data and sometimes i have lockups that force me for unsafe resumes. can this trigger the need for a rebuild tree? and, if you have experiences with it, do you know what could happen without fsck on an unsafely unmounted luks partition?
thanks. -- dott. ing. beso
