From: Phillip Susi <psusi@ubuntu.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Ted Ts'o <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: mkfs.ext4 vs. e2fsck discard oddities
Date: Fri, 09 Mar 2012 10:14:18 -0500 [thread overview]
Message-ID: <4F5A1E4A.9060804@ubuntu.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1203090957190.4487@dhcp-27-109.brq.redhat.com>
On 3/9/2012 3:59 AM, Lukas Czerner wrote:
> Why would we try to check UNINIT groups with valid descriptor checksums
> ? I think that this problem will be solved with BLOCK_DISCARDED flag as
> we discussed with Ted in another thread. No need to have yet another
> option so it is win-win :)
Because not skipping a specific action on an uninitialized group (
discard ) is a specific case of the more general form of not skipping
uninitialized groups. I thought that it might sometimes be useful to
actually verify the group is correct instead of trusting the uninit
flag, especially if you are about to discard it. Also any other things
that are added in the future and skipped for uninit groups would not
need yet another flag to specifically not skip that action, since it
will be covered by the more general flag already.
Also the way the code was structured it looked like it would be much
simpler to bypass the skip and do the full check of the uninit group
than to modify it to discard the group even though checking it was skipped.
prev parent reply other threads:[~2012-03-09 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 17:34 mkfs.ext4 vs. e2fsck discard oddities Eric Sandeen
2012-02-29 7:12 ` Lukas Czerner
2012-02-29 16:01 ` Eric Sandeen
2012-03-01 4:47 ` Theodore Tso
2012-03-01 7:12 ` Lukas Czerner
2012-03-01 14:38 ` Ted Ts'o
2012-03-01 14:54 ` Lukas Czerner
2012-03-08 16:48 ` Phillip Susi
2012-03-09 8:59 ` Lukas Czerner
2012-03-09 15:14 ` Phillip Susi [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=4F5A1E4A.9060804@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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.