Re: fsck more often when powerfail is detected (was Re: wishfulthinking about atomic, multi-sector or full MD stripe width, writes instorage)

[Pavel Machek]

On Sun 2010-04-04 12:59:16, Rob Landley wrote:
> On Sunday 04 April 2010 08:47:29 Pavel Machek wrote:
> > Maybe there's time to reviwe the patch to increase mount count by >1
> > when journal is replayed, to do fsck more often when powerfails are
> > present?
> 
> Wow, you mean there are Linux users left who _don't_ rip that out?

Yes, there are. It actually helped pinpoint corruption here, 4 time it
was major corruption.

And yes, I'd like fsck more often, when they are power failures and
less often when the shutdowns are orderly...

I'm not sure of what right intervals between check are for you, but
I'd say that fsck once a year or every 100 mounts or every 10 power
failures is probably good idea for everybody...

> The auto-fsck stuff is an instance of "we the developers know what you the 
> users need far more than you ever could, so let me ram this down your throat".  
> I don't know of a server anywhere that can afford an unscheduled extra four 
> hours of downtime due to the system deciding to fsck itself, and I don't know 
> a Linux laptop user anywhere who would be happy to fire up their laptop and 
> suddenly be told "oh, you can't do anything with it for two hours, and you 
> can't power it down either".

On laptop situation is easy. Pull the plug, hit reset, wait for fsck,
plug AC back in. Done that, too :-).

Yep, it would be nice if fsck had "escape" button.

> I'm all for btrfs coming along and being able to fsck itself behind my back 
> where I don't have to care about it.  (Although I want to tell it _not_ to do 
> that when on battery power.)  But the "fsck lottery" at powerup is just 
> stupid.

fsck lottery. :-).
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/