From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Ryan, Michael" <Michael.Ryan2@lenovoemc.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Please summarize state of ext4 resize >16TB
Date: Wed, 8 Jan 2014 11:30:18 -0800 [thread overview]
Message-ID: <20140108193018.GF9229@birch.djwong.org> (raw)
In-Reply-To: <BBC8F4C34A7B5A4DB487459885025E7F018A0BAE0391@EXCLUSTER.iomegacorp.com>
On Wed, Jan 08, 2014 at 12:14:17PM -0700, Ryan, Michael wrote:
> I've been searching for info on the ability to resize ext4 from <16TB to
> >16TB. This was not supported in the past and I've received conflicting
> >information as to if/when this is/will be supported. I've also seen
> >indications that on disk data structures must be changed for this resize to
> >work.
>
> Is this capability currently supported?
> If so, what kernel level (and resize2fs level) is necessary? Are there
> restrictions as to options at mkfs time? If not, is this planned for a
> future release? Or is this just not possible or practical due to on disk
> structures and is likely to never be supported?
In most cases it's necessary to turn on 64bit (the feature flag) to cross the
16T boundary. I've had patches against resize2fs to add this ability--it
involves moving data blocks and rewriting group descriptors--on the list for a
few months, but I don't know of Ted's plans to put them in a release. Probably
post-1.43, is my guess.
I don't have any kernel patches to turn on 64bit, and I haven't any current
plans to make any.
--D
>
> Thank you.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-01-08 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 19:14 Please summarize state of ext4 resize >16TB Ryan, Michael
2014-01-08 19:30 ` Darrick J. Wong [this message]
2014-01-08 20:04 ` Theodore Ts'o
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=20140108193018.GF9229@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=Michael.Ryan2@lenovoemc.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;
as well as URLs for NNTP newsgroup(s).