All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Theodore Tso <tytso@mit.edu>,
	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: Thu, 24 May 2007 17:39:11 +0000	[thread overview]
Message-ID: <20070524173911.GA4541@ucw.cz> (raw)
In-Reply-To: <20070522180158.GA4668@thunk.org>

Hi!

> > > #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:

Right. Could we get more helpful message here? 'Filesystem check on
next boot on AC power'? Or maybe keep counting, and when we reach 2x
mount-count-limit, force a fsck, battery power or not?

> [options]
> 	defer_check_on_battery = false

I guess openembedded people should make this default on zauruses...

> 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.

I'll just remember to do it manually, I guess. 

But here's what I've got:

oot@spitz:/home/pavel# fsck.ext2 -f /dev/hda3
e2fsck 1.38 (30-Jun-2005)
Pass 1: Checking inodes, blocks, and sizes
Inode 371989 has illegal block(s).  Clear<y>? yes

Illegal block #2 (134217728) in inode 371989.  CLEARED.
Pass 2: Checking directory structure

i_file_acl for inode 371988 (/home/root/misc/zaurus/smail) is 131072,
should be zero.
Clear<y>? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -339972 +471044
Fix<y>? yes

Free blocks count wrong for group #10 (13882, counted=13883).
Fix<y>? yes

...kernel 2.6.16-preempt (on zaurus). Filesystem should have been clean -- I was
using it till crash for half a year, but that's what journal is for,
right? ...But I guess this is almost impossible to debug?

							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-05-26  9:31 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
2007-05-24 17:39           ` Pavel Machek [this message]
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=20070524173911.GA4541@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ext3-users@redhat.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.