On 2011-12-24 09:02:49 (+0100), jdd wrote:
Le 24/12/2011 07:40, Jon Clausen a écrit :
These days I rarely use 'ext' filesystems for anything but /boot/, but I've walked into the "unexpected fsck" enough times that I can see some value in at least being forewarned.
do you have any number on the fsck time? I just has a checkout of my desktop (2 drives, 1 and 2 Tb) and it was less than one minute (ext4), so the waiting time is manageable. (openSUSE 12.1)
well, I guess it depends... It's been a while since last time, but for large filesystems it can certainly be long enough to go "argh, damnations! I don't have time for this right now"
I think having it at shutdown is worst, because, I often shutdown in a hurry (not having time to look at messages). But a waiting time with ability to disable the control at boot could be a good solution, if I boot in a hurry, usually I'm in front of the computer, waiting and I can answer
There is that, but if it's some headless or remote system, I'd like to know if fsck is imminent. In case of 'server' systems with long uptimes, it's more or less guaranteed that any 'ext' filesystems will have gone beyond the 'number of days' limit. In some cases there were somewhat large but 'secondary' (as in nonessential 'data' or 'backup') ext filesystems which might very well have been unmounted and fsck'ed prior to rebooting - but instead ended up delaying the boot to the point where one started wondering WTF happened... Obvioulsy the prudent thing would be to investigate that sort of thing beforehand, but sometimes we forget :P A boot-time "to fsck or not to fsck?" timeout IMHO would be even worse though, since that would just introduce a further delay - unless the default would be to proceed *without* fsck, which might not be such a great idea... /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org