From: TR Reardon <thomas_reardon@hotmail.com>
To: linux-ext4@vger.kernel.org
Subject: Reserved GDT inode: blocks vs extents
Date: Fri, 19 Sep 2014 11:54:39 -0400 [thread overview]
Message-ID: <BAY406-EAS150EB9E4098E2894ADA30B7FDB40@phx.gbl> (raw)
Hello all: there's probably a good reason for this, but I'm wondering why inode#7 (reserved GDT blocks) is always created with a block map rather than extent?
[see ext2fs_create_resize_inode()]
Would changing this to extent resolve problem of resize_inode and 64bit / >16TB filesystems?
next reply other threads:[~2014-09-19 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 15:54 TR Reardon [this message]
2014-09-19 16:36 ` Reserved GDT inode: blocks vs extents Theodore Ts'o
2014-09-19 17:26 ` TR Reardon
2014-09-19 19:48 ` Andreas Dilger
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=BAY406-EAS150EB9E4098E2894ADA30B7FDB40@phx.gbl \
--to=thomas_reardon@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox