From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] extending a logical volume
Date: Tue Jan 22 04:37:02 2002 [thread overview]
Message-ID: <20020122113326.A23531@sistina.com> (raw)
In-Reply-To: <20020121193331.I4014@lynx.turbolabs.com>; from adilger@turbolabs.com on Mon, Jan 21, 2002 at 07:33:31PM -0700
On Mon, Jan 21, 2002 at 07:33:31PM -0700, Andreas Dilger wrote:
> On Jan 21, 2002 12:40 -0600, lembark@wrkhors.com wrote:
> > 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].
>
> I agree about the backups. Most people don't think about
> backups until it is too late. I disagree about only doing
> resizing at some late hour in the night though. Many times
> there are unexpected demands on storage, and the sysadmin
> doesn't have control over the cause, but gets blamed for
> the effect (i.e. running out of space). Hence, online fs
> resizing is a critical operation for an enterprise system.
>
> > Even HP's LVM -- probably the most forgiving of all --
> > has to be dismounted for extendfs; lvextend can be run
> > any time you like.
>
> ??? That was only with the old HP LVM filesystem (UFS I think).
> If you formatted with the new filesystem (can't remember the name),
Andreas,
they got a Veritas license for vxfs and that could be online grown but
you couldn't shrink it without purchasing an additional license.
> you could do online resizing. AIX has had online resizing forever,
> and so has XFS. None of these allow even offline shrinking though,
> which ext2/ext3 does.
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-01-22 4:37 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 [this message]
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=20020122113326.A23531@sistina.com \
--to=mauelshagen@sistina.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