[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: fs periodic check (was Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted)
- From: Theodore Tso <tytso mit edu>
- To: Pavel Machek <pavel ucw cz>
- Cc: Jesper Juhl <jesper juhl gmail com>, Martin Mokrejs <mmokrejs ribosome natur cuni cz>, linux-kernel vger kernel org, ext3-users redhat com
- Subject: Re: fs periodic check (was Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted)
- Date: Tue, 22 May 2007 14:01:59 -0400
On Sun, May 20, 2007 at 07:55:26PM +0000, Pavel Machek wrote:
> > #1, This is why periodic checks are a good thing; it catches problems
> > that could stay hidden and result in data loss sooner rather later.
>
> Actually, I see something funny with periodic checks here. It claims
> 'filesystem check on next boot' for >10 boots now.
>
> It is sharp zaurus machine, and the filesystem tends to _never_ be
> unmounted correctly (broken scripts), so I get journal replay each
> time.
The Sharp Zaurus is a PDA which is almost always running on battery,
right? You need to add to /etc/e2fsck.conf:
[options]
defer_check_on_battery = false
See the e2fsck.conf man page for more details, but basically, e2fsck
was optimized for x86 laptops that have such lousy batttery life that
people generally try to run AC adapters to avoid killing the laptop
battery --- and for which running a spinning hard drive platters for
an extended time to fsck a 100GB drive might not be such a hot idea.
So we try to defer the periodic fsck until the laptop is back on AC
power. But for a PDA running a flash drive which is almost always
running on battery you'll want to change the default using
e2fsck.conf.
- Ted
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]