From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] resizing a mounted ext2 file system?
Date: Mon, 12 Mar 2001 11:11:33 -0700 (MST) [thread overview]
Message-ID: <200103121811.f2CIBXw04818@webber.adilger.int> (raw)
In-Reply-To: <m2pufnc7ya.fsf@isnogud.escape.de> from Urs Thuermann at "Mar 12, 2001 04:39:41 pm"
Urs writes:
> IIRC, I have read somewhere of the possibility to resize a mounted
> ext2 file system. I think I will have to patch the kernel and the
> resize2fs utility (or install a new utility) to be able to do it.
>
> Can someone give me a URL or other pointer, where to find it? How
> stable is this? And will this go into the mainstream kernel/e2fsprogs
> in near future?
Please see http://sourceforge.net/projects/ext2resize/
It is fairly stable (OK, I'm a bit biased), but I haven't had any bug
reports in many months (1 year+?). It only works on x86 right now.
Will it go into kernel? Eventually. I'm working on a new ext3 version
right now, and I haven't tried submitting the ext2 version to Linus in a
long time.
The new ext3 code will need a few minor changes to the on-disk layout
of the resize inode (the old layout will still work for ext2). At this
point I will add an ext2 COMPAT flag, add full e2fsck support (verification
of resize inode instead of just removing an error message like now), and
send patches to Ted for inclusion into e2fsprogs (he will probably accept).
Once all is installed, you can use e2fsadm to handle LV+ext2 resize (it
will call ext2online or ext2resize as appropriate).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
prev parent reply other threads:[~2001-03-12 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 15:39 [linux-lvm] resizing a mounted ext2 file system? Urs Thuermann
2001-03-12 18:11 ` 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=200103121811.f2CIBXw04818@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=linux-lvm@sistina.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).