From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] while file system?
Date: Mon, 30 Jan 2006 16:32:46 -0500 [thread overview]
Message-ID: <20060130213246.GA4223@ti64.telemetry-investments.com> (raw)
In-Reply-To: <E1F3esb-0001Wr-7x@highlab.com>
On Mon, Jan 30, 2006 at 12:40:01PM -0700, Sebastian Kuzminsky wrote:
> Looks like Ext3 supports online grow, but only up to +16 GB, which
> makes it useless on modern disks, much less arrays of modern disks....
> Looks like offline grow & shrink are unlimited, which is good. Lots of
> old (unmaintained?) tools and kernel patches here, but lots of recent
> activity too. What's the current status?
Andreas Dilger's out-of-tree implementation of ext2/ext3 online resize
allowed one to run ext2prepare in order to prepare the filesystem for much
larger resizes. [The code can be found here: ext2resize.sf.net.]
The ext2prepare(8) man page says:
The ext2prepare command modifies an unmounted ext2 filesystem
on device so that ext2online(8) program can later resize the
mounted filesystem to be at least as large as size although the
actual maximum size will be some larger multiple of various
filesystem parameters. While ext2prepare must be run on
an unmounted filesystem, device does not have to currently be
as large as size. This allows one to later increase the
size of device and do the resize while the filesystem is mounted.
On the way toward kernel inclusion, a number of things changed, and some
changes were made to e2fsprogs for compatibility.
The e2fsprogs-1.38 mke2fs(8) man page on Fedora Core 4, under the OPTIONS section,
says:
resize=max-online-resize
Reserve enough space so that the block group descriptor table can
grow to support a filesystem that has max-online-resize blocks.
You can easily test it with a huge sparse file, i.e.,
dd if=/dev/zero of=/tmp/image.bin bs=4K seek=500000000 count=1 # ~2TB
mkdir /tmp/mnt
losetup /dev/loop0 /tmp/image.bin
mke2fs -b 4096 -j -E resize=2147483648 /dev/loop0 134217728 # 512GB, resize 8TB.
mount /dev/loop0 /tmp/mnt
df /tmp/mnt
ext2online /tmp/mnt
df /tmp/mnt
Make sure that you have 20GB or so of space on partition where you
create the image.bin.
Regards,
Bill Rugolsky
next prev parent reply other threads:[~2006-01-30 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 19:40 [linux-lvm] while file system? Sebastian Kuzminsky
2006-01-30 21:32 ` Bill Rugolsky Jr. [this message]
2006-01-31 0:56 ` Zac Slade
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=20060130213246.GA4223@ti64.telemetry-investments.com \
--to=brugolsky@telemetry-investments.com \
--cc=linux-lvm@redhat.com \
/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).