On Monday 30 November 2009 18:09:07 Maxim Wexler wrote: > aarrrgh!! I'm the one with the netbook!! The default didn't work. > Checking fs every boot does. Extra reboot time amounts to a few secs > vs not booting at all, dammit!
You are missing the point. That behaviour is wrong and I cannot overstate that enough. If your system requires an fsck at every boot to even reboot at all, then there is something badly wrong with your filesystem. Enabling an fsck at every boot for ext2 is merely working around the problem at another level and not addressing the actual problem. So please stop arguing with people who are trying to help you and instead find out why your system is exhibiting incorrect behaviour. My first guess is that the filesystem is not being correctly unmounted at shutdown and is therefore marked as dirty at next startup. Ext2 does require an fsck under those circumstances as the chances of data corruption are vastly increased - the assumption being that power to the machine was probably removed abruptly. There could be many reasons for this and you will have to investigate your shutdown process carefully. Do you disagree with my logic as stated above? > > On 11/30/09, Alan McKinnon <alan.mckin...@gmail.com> wrote: > > On Monday 30 November 2009 05:40:31 Maxim Wexler wrote: > >> > Right. > >> > >> wrong > >> > >> > Of course, if there are serious filesystem structural problems you'll > >> > want to get them solved, but it's either a LiveCD chroot or disable > >> > fsck at boot. > >> > >> There's nothing wrong with the filesystem. It's ext2 and requires > >> being checked at every boot. > > > > Wrong. There is no need to fsck ext2 at every boot. The default is to > > check it > > every 26 mounts. You can change that if you want, and send your reboot > > times sky-high.. > > > >> Before that it wouldn't boot at all. > > > > That would appear to be a completely separate issue. > > > > -- > > alan dot mckinnon at gmail dot com > -- alan dot mckinnon at gmail dot com
