From: Andreas Dilger <adilger@sun.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: LKML <linux-fsdevel@vger.kernel.org>
Subject: Re: how to online resize ext3 when fs does not support it?
Date: Wed, 02 Jul 2008 02:15:33 -0600 [thread overview]
Message-ID: <20080702081533.GX6239@webber.adilger.int> (raw)
In-Reply-To: <4868AC09.7050101@wpkg.org>
On Jun 30, 2008 11:48 +0200, Tomasz Chmielewski wrote:
> I have a fairly large ext3 filesystem created some time ago, which
> doesn't support online resizing.
>
> # resize2fs -p /dev/sdaz
> resize2fs 1.40.2 (12-Jul-2007)
> Filesystem at /dev/sdaz is mounted on /mnt/iscsi_backup; on-line
> resizing required
> old desc_blocks = 77, new_desc_blocks = 87
> resize2fs: Filesystem does not support online resizing
>
>
> Is is possible to add resize_inode feature to an existing ext3 filesystem?
>
> My tune2fs manual (from e2fsprogs 1.40.2) doesn't state adding
> "resize_inode" is possible, and newer e2fsprogs releases only support
> removing resize_inode feature.
> Will adding resize_inode be supported in the future, or is it definitely
> "is not, won't be possible"?
Adding "resize_inode" feature to an existing filesystem is possible with
an old tool called "ext2prepare", part of "ext2resize" tools I wrote.
I've long given up maintaining those tools, but it is possible your
filesystem is also old enough to not have any of the incompatible
features that might confuse ext2prepare.
I'd suggest having a backup of your filesystem in any case, because that
is just prudent behaviour, as there is always a non-zero risk of problems
during resize.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
prev parent reply other threads:[~2008-07-02 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 9:48 how to online resize ext3 when fs does not support it? Tomasz Chmielewski
2008-07-02 8:15 ` Andreas Dilger [this message]
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=20080702081533.GX6239@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mangoo@wpkg.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).