All of lore.kernel.org
 help / color / mirror / Atom feed
From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] extending a logical volume
Date: Mon Jan 21 12:43:02 2002	[thread overview]
Message-ID: <12230000.1011638456@duke.wrkhors.com> (raw)
In-Reply-To: <E16Sist-000136-00@arwen.dev33.cvf>


-- Pierrick PONS <ppons@cvf.fr> on 01/21/02 19:09:31 +0100

> 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.
> 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.
> 
> I've seen that a ext2online patch does exist, maybe this fonctionnality is 
> still implemented in a newer kernel ?
> 
> Could you give me, if it exists, a method to extend the size without unmount 
> the logical volume ?
> 
> Thank's a lot.

Put it another way: You can lvextend a mounted volume. 
There isn't any good way to extend the file system while
it's mounted. Adding the cyl groups to a mounted file 
system would blow up several parts of the VFS layer.
Since extending the LVM takes O(ms) to finish there 
isn't much gain in doing it mounted anyway. 

The simplest way to handle it is unmounting, fsck-ing
and re-mounting the thing immediately after your weekly
backup, when users have to be off the system anyway
[if you want to tell me that the system is too important
to offline for a backup I'd strongly suggest finding a 
9-story window near the console, it'll be easier to 
handle it yourself than have the users do it for you 
after a crash looses all of the data].

If the sytsem is used for real-time processing then
simply switch to the backup server for 10 minutes, 
extend and validate the system then switch back.

Total time for, say, 100GB file system doubling in 
size would be 60 seconds on any reasonably fast I/O
system, nearly all of which is spent extending the 
filesystem.

Even HP's LVM -- probably the most forgiving of all -- 
has to be dismounted for extendfs; lvextend can be run
any time you like.

--
Steven Lembark                              2930 W. Palmer
Workhorse Computing                      Chicago, IL 60647
                                           +1 800 762 1582

  reply	other threads:[~2002-01-21 12:43 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 [this message]
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
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=12230000.1011638456@duke.wrkhors.com \
    --to=lembark@wrkhors.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 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.