public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Martin Mokrejs <mmokrejs@ribosome.natur.cuni.cz>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	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	[thread overview]
Message-ID: <20070522180158.GA4668@thunk.org> (raw)
In-Reply-To: <20070520195526.GA5235@ucw.cz>

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


  reply	other threads:[~2007-05-22 21:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  9:06 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted Martin Mokrejs
2007-05-18  9:53 ` Martin Zwickel
2007-05-18 11:47 ` Kalpak Shah
2007-05-18 13:51   ` Martin Mokrejs
2007-05-18 14:08     ` Kalpak Shah
2007-05-18 14:32       ` Martin Mokrejs
2007-05-18 14:20 ` Jesper Juhl
2007-05-18 14:35   ` Martin Mokrejs
2007-05-18 21:57     ` Theodore Tso
2007-05-20 19:55       ` fs periodic check (was Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted) Pavel Machek
2007-05-22 18:01         ` Theodore Tso [this message]
2007-05-24 17:39           ` Pavel Machek
2007-05-28 12:38             ` Jan Kara
2007-05-28 13:03               ` Pavel Machek
2007-05-29  2:55             ` Theodore Tso
2007-05-29  3:05               ` Neil Brown
2007-05-29 11:38                 ` Pavel Machek
2007-05-29 11:34               ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070522180158.GA4668@thunk.org \
    --to=tytso@mit.edu \
    --cc=ext3-users@redhat.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox