linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Jelle de Jong <jelledejong@powercraft.nl>
Cc: linux-ext4@vger.kernel.org
Subject: Re: How to resize to an bigger then 16TB ext4 filesysteem on Debian
Date: Thu, 10 Apr 2014 10:09:37 -0400	[thread overview]
Message-ID: <20140410140937.GE15925@thunk.org> (raw)
In-Reply-To: <53468055.4070700@powercraft.nl>

On Thu, Apr 10, 2014 at 01:28:21PM +0200, Jelle de Jong wrote:
> 
> Hello everyone,
> 
> https://packages.debian.org/wheezy/e2fsprogs
> 
> # resize2fs /dev/lvm0-vol/storage
> resize2fs 1.42.5 (29-Jul-2012)
> resize2fs: New size too large to be expressed in 32 bits
> 
> (will the command work with e2fsprogs 1.42.9-3?)
> 
> # tune2fs -l /dev/lvm0-vol/storage
> http://paste.debian.net/92889/
> 
> Suggestions has to be stable enough for production systems.

I'm going to assume the file system was created without having the
64-bit file system feature set.  (Running dumpe2fs -h
/dev/lvm0-vol/storage can verify this).

If that's true, and you require a production-stable way of doing this,
there's really only one thing I can suggest:

1)  Backup your file system completely
2)  Get the development version of e2fsprogs, and apply a set of
    in-development patches that haven't yet been merged
3)  Use this in-development resize2fs to convert to a 64-bit file system,
    realizing that it will have completely rewrite your inode tables.
    Cross your fingers.
4)  If it works, you're done.  If not, you can restore from backups.  :-)

So basically steps 2 and 3 are ways of optimizing needing to do a full
restore of your file system.....

Cheers,

					- Ted

  reply	other threads:[~2014-04-10 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 11:28 How to resize to an bigger then 16TB ext4 filesysteem on Debian Jelle de Jong
2014-04-10 14:09 ` Theodore Ts'o [this message]
2014-04-10 15:07   ` Jelle de Jong
2014-04-11  0:22     ` 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=20140410140937.GE15925@thunk.org \
    --to=tytso@mit.edu \
    --cc=jelledejong@powercraft.nl \
    --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).