From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: fallocated blocks past EOF & past parent node range OK?
Date: Mon, 15 Jul 2013 10:19:12 -0500 [thread overview]
Message-ID: <51E412F0.3040206@redhat.com> (raw)
I'm sorry I missed the conversation earlier this morning, but ewhitney let me know that the consensus was that for fallocated blocks past EOF, it's fine to have those blocks live outside the parent node's range in the extent tree.
This seems quite strange to me, and unexpected.
What is the rationale for this? Why would these past-EOF extents look unique in the extent tree, and not be covered by the parent node?
Thanks,
-Eric
reply other threads:[~2013-07-15 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51E412F0.3040206@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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.