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: Mon, 28 May 2007 22:55:34 -0400 [thread overview]
Message-ID: <20070529025534.GD24003@thunk.org> (raw)
In-Reply-To: <20070524173911.GA4541@ucw.cz>
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
next prev parent reply other threads:[~2007-05-29 2:55 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
2007-05-28 12:38 ` Jan Kara
2007-05-28 13:03 ` Pavel Machek
2007-05-29 2:55 ` Theodore Tso [this message]
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=20070529025534.GD24003@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