From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] resize2fs: relax requirements for -P output a bit
Date: Sat, 17 Jul 2010 06:37:50 -0400 [thread overview]
Message-ID: <20100717103750.GA4684@thunk.org> (raw)
In-Reply-To: <4C3B5EA0.3040904@redhat.com>
On Mon, Jul 12, 2010 at 01:27:44PM -0500, Eric Sandeen wrote:
> Requiring an immediate pre-fsck before printing a minimum
> resize size seems a bit draconian; if the fs isn't clean or marked
> with error, then certainly, but for an informational minimum
> size, I don't think we need to require a fsck since last mount.
>
> I had simply copied the checks from the actual resize path,
> previously.
>
> Installers use this option (-P) to gather minimum resize info,
> and requiring an actual fsck before use just seems to go too far.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Makes sense. I've added it to the e2fsprogs maint branch.
- Ted
prev parent reply other threads:[~2010-07-18 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 18:27 [PATCH] resize2fs: relax requirements for -P output a bit Eric Sandeen
2010-07-17 10:37 ` Ted Ts'o [this message]
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=20100717103750.GA4684@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).