linux-kernel - Re: 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: <20070529025534.GD24003@thunk.org>
Date:	Mon, 28 May 2007 22:55:34 -0400
From:	Theodore Tso <tytso@....edu>
To:	Pavel Machek <pavel@....cz>
Cc:	Martin Mokrejs <mmokrejs@...osome.natur.cuni.cz>,
	Jesper Juhl <jesper.juhl@...il.com>,
	linux-kernel@...r.kernel.org, ext3-users@...hat.com
Subject: Re: fs periodic check (was Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted)

On Thu, May 24, 2007 at 05:39:11PM +0000, Pavel Machek wrote:
> Right. Could we get more helpful message here? 'Filesystem check on
> next boot on AC power'? 

So "(check deferred; on battery)" wasn't explicit enough?  I guess I
assumed that users would understand that the opposite of "on battery"
was "on AC power".  I guess I could say "(check defferred 'til on AC
power)" if people think it would be clearer.

> Or maybe keep counting, and when we reach 2x mount-count-limit,
> force a fsck, battery power or not?

We do that already.  It's just tough to make that all fit on an 80
status message.  :-)

						- Ted
-
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/