From: Andreas Dilger <adilger@clusterfs.com>
To: Joseph Kezar <jkezar@doc.state.vt.us>
Cc: Linux LVM Sistina <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] LVM ext3 and lvreduce
Date: Wed Nov 13 11:02:02 2002 [thread overview]
Message-ID: <20021113165953.GB9930@clusterfs.com> (raw)
In-Reply-To: <1037195718.3126.4.camel@corr11.doc.state.vt.us>
On Nov 13, 2002 08:55 -0500, Joseph Kezar wrote:
> I have LVM working, and I have created all my logical volumes for my
> environment. All of my logical volumes have been mkfs.ext3'd.
> Everything works, except for when I try to change the size with lvreduce
> or lvextend. These tools are happy to work, but when I remount my
> logvols and type: mount I see that in fact the size that is reported to
> the OS has not changed.
>
> Is there any incompatabilities with LVM and Ext3?
No - ext3 is totally independent of LVM, except if you are doing snapshots.
> Is there a comparable tool for ext3 like e2fsadm?
Yes, e2fsadm.
> Is it possible to resize an ext3 partition while it is online?
Yes, but you need a new kernel patch and ext2online tools from CVS.
Find both at http://sourceforge.net/projects/ext2resize/
This is beta code now (i.e. we don't know of any bugs), excluding the
fact that ext2prepare doesn't work yet, so you can't online resize
past the next 16GB boundary unless you created a new filesystem with
the patched "mke2fs -O resize_inode" (patch at same place).
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
prev parent reply other threads:[~2002-11-13 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 7:55 [linux-lvm] LVM ext3 and lvreduce Joseph Kezar
2002-11-13 8:05 ` Pierre Lamb
2002-11-13 8:05 ` Heinz J . Mauelshagen
2002-11-13 11:02 ` 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=20021113165953.GB9930@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=jkezar@doc.state.vt.us \
--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 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.