From: Pierrick PONS <ppons@cvf.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] extending a logical volume
Date: Tue Jan 22 05:09:01 2002 [thread overview]
Message-ID: <E16Syml-0004V1-00@arwen.dev33.cvf> (raw)
In-Reply-To: Your message of "Mon, 21 Jan 2002 19:28:59 MST." <20020121192859.H4014@lynx.turbolabs.com>
> On Jan 21, 2002 19:09 +0100, Pierrick PONS wrote:
> > I've read the extending logical volume section and I can't believe this.
> > According to the doc, it would be impossible to extend a logical volume
> > without unmounting it first.
>
> LV resize != fs resize.
>
Yes you're right. It's possible to extend LV online but it's not the same for
file systems.
> > I'm using a ext3 (with a 2.4.17 kernel) filesystem and I'd like to extend my
> > logical volume without unmounting it first. This would be used on a
> > production server, so I can't unmount any logical volume.
>
> Currently, you cannot online resize ext3, but that is only because the code
> which I wrote to do this for 2.2 was never released, and it has not been
> ported to 2.4/2.5 yet.
>
It would be a really goud feature .... :-)
> > I've seen that a ext2online patch does exist, maybe this fonctionnality is
> > still implemented in a newer kernel ?
>
> No, still only available as a patch. The ext2 online resizing patch is
> very solid. The ext3 code is, by necessity, a total rewrite of the code
> to work with ext3 journaling, but the fundamental concepts are the same.
>
> > Could you give me, if it exists, a method to extend the size without unmount
> > the logical volume ?
>
> Use ext2 + ext2online patch (not great, because you probably crash more
> often than you need to resize), use ext3 but no online resizing (offline
> resizing works just fine with ext2resize), or work on porting the ext3
> resizing code to 2.4.
>
hmmm, I'm not good enough to code this :-(
So you'd rather use ext3 with offline resizing.
That is a real problem because LVM would be used on a 24/24 available data
server with nfs accesses . Datas should be get as often as the other servers
need to.
Maybe I should have a look at reiserfs + resize-reiserfs instead of using ext3
. What a pitty, ext3 is easy to install and is jouralised.
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
>
>
Thank you Andreas .
Pierrick
next prev parent reply other threads:[~2002-01-22 5:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 12:10 [linux-lvm] extending a logical volume Pierrick PONS
2002-01-21 12:43 ` lembark
2002-01-21 14:13 ` Brad Langhorst
2002-01-21 14:50 ` Harri Haataja
2002-01-21 15:01 ` lembark
2002-01-21 18:47 ` [linux-lvm] Whats wrong with this picture? James Hawtin
2002-01-21 20:37 ` Andreas Dilger
2002-01-22 3:22 ` James Hawtin
2002-01-21 15:22 ` [linux-lvm] extending a logical volume mitch
2002-01-21 15:37 ` Harri Haataja
2002-01-21 18:27 ` James Hawtin
2002-01-21 14:56 ` lembark
2002-01-21 20:40 ` Andreas Dilger
2002-01-21 14:59 ` Pierrick PONS
2002-01-21 15:04 ` lembark
2002-01-21 20:34 ` Andreas Dilger
2002-01-22 4:37 ` Heinz J . Mauelshagen
2002-01-21 20:29 ` Andreas Dilger
2002-01-22 5:09 ` Pierrick PONS [this message]
2002-01-22 6:17 ` James Hawtin
2002-01-22 13:04 ` Andreas Dilger
2002-01-23 9:09 ` Pierrick PONS
2002-01-23 11:40 ` Andreas Dilger
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=E16Syml-0004V1-00@arwen.dev33.cvf \
--to=ppons@cvf.fr \
--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