linux-kernel - fs periodic check (was Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070520195526.GA5235@ucw.cz>
Date:	Sun, 20 May 2007 19:55:26 +0000
From:	Pavel Machek <pavel@....cz>
To:	Theodore Tso <tytso@....edu>,
	Martin Mokrejs <mmokrejs@...osome.natur.cuni.cz>,
	Jesper Juhl <jesper.juhl@...il.com>,
	linux-kernel@...r.kernel.org, ext3-users@...hat.com
Subject: fs periodic check (was Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted)

Hi!

> > >  How do you know that the corruption was caused by 2.6.21-rc1 ?
> > >  Isn't it possible that the corruption was created by an earlier
> > >  kernel, but only detected when a forced fsck was run - which just
> > >  happened to be while you were running 2.6.21-rc1 ...
> > > 
> > >  My point is that, as far as I can see, there's nothing tying
> > >  2.6.21-rc1 specifically to this corruption... or?
> > 
> > You might be right, but I thought maybe more probably is the cause in kernel
> > as that is what I have changed recently. ;) Or maybe someone can at leats say
> > "No, no changes to be considered between 2.6.20.6 and 2.6.22-rc1.". ;)
> 
> Well, given that your e2fsck transcript started with this:
> 
> > /dev/hda3 has been mounted 38 times without being checked, check forced
> 
> #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.

Anyone else sees that?
							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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/