All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zheng Liu <gnehzuil.liu@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Michael <mike@draftx.net>, Theodore Ts'o <tytso@mit.edu>,
	linux-ext4@vger.kernel.org
Subject: Re: EXT4 Larger Than 16TB
Date: Mon, 22 Jul 2013 07:43:26 +0800	[thread overview]
Message-ID: <20130721234325.GA15659@gmail.com> (raw)
In-Reply-To: <51EC64E8.8090509@zytor.com>

On Sun, Jul 21, 2013 at 03:47:04PM -0700, H. Peter Anvin wrote:
> On 07/09/2013 06:45 AM, Michael wrote:
> > No problem, it sounds like it would be a very tricky bit of code to
> > write. Shuffling metadata blocks is not an easy feat.
> > 
> > Is there any way to tell if I'm using 64 bit? Ubuntu defaults to
> > setting ext4 to default, but I don't know if it did when I first
> > created this FS.
> > 
> > If it is 64 bit, the resize2fs utility should be able to handle this
> > one kernels >3.7, correct?
> > 
> 
> Is there a way to force this at mkfs time?  I.e. "I know I may want to
> expand this filesystem beyond the 16 TB point?"

Hi Peter,

You could use 'mkfs.ext4 -O 64bit' to force enable 64bit support.  In
addition, we will enable this feature by default.  Lukas has a patch to
fix it.  Here is the link [1].

1. http://patchwork.ozlabs.org/patch/253234/

Regards,
                                                - Zheng

  reply	other threads:[~2013-07-21 23:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 21:32 EXT4 Larger Than 16TB Michael
2013-07-09  2:14 ` Theodore Ts'o
2013-07-09 13:45   ` Michael
2013-07-21 22:47     ` H. Peter Anvin
2013-07-21 23:43       ` Zheng Liu [this message]
2013-07-22  0:44         ` Michael
2013-07-22  0:52           ` Zheng Liu
2013-07-22  0:59             ` Michael

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=20130721234325.GA15659@gmail.com \
    --to=gnehzuil.liu@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mike@draftx.net \
    --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.