public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Jolet <john@jolet.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo LVM Newbie Question
Date: Fri, 24 Feb 2006 22:13:05 -0600	[thread overview]
Message-ID: <5283AACA-DC0D-409D-A67A-0BCC9666AC14@jolet.net> (raw)
In-Reply-To: <200602242135.00930.krakrjak@volumehost.net>


On Feb 24, 2006, at 9:35 PM, Zac Slade wrote:

> On Friday 24 February 2006 00:03, Alexander Skwar wrote:
>> John Jolet wrote:
>>> Remember, the fs cannot be mounted when you extend it.
>>
>> That's wrong. Every FS can be extended online, even ext{2,3}
>> with certain patches IIRC.
> WRONG!!! (or partially anyway)  Here's the rundown:
> reiser3, resizable online in two ways
> 	1)resize_reiserfs /path/to/dev
> 	2)mount -o remount,resize /path/to/dev
> XFS, MUST be mounted to resize use xfs_grow /mount/point
> JFS, resizable online with a mount -o remount,resize /path/to/dev
> ext2/3, resizable offline reliably.  Online resize is a *very*  
> experimental
> experiment.  Have good backups.
>
> For a good reference if one is ever needed to give to a friend,  
> relative or
> foe try http://www.tldp.org/HOWTO/LVM-HOWTO/extendlv.html
okay, i'll rephrase.... being an old aix hand... with the (possible)  
exeption of reiser.... I, personally, would not trust any filesystem  
to resize without being unmounted.  but then, compared to the aix  
lvm, which can be resized with oracle accessing at full speed, linux  
lvms are just barely getting to what I'd call "production ready".   
interesting to see that we're moving in an online-resizable direction  
on linux. :)

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-25  4:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 20:22 [gentoo-user] Gentoo LVM Newbie Question CR Little
2006-02-23 20:41 ` Boyd Stephen Smith Jr.
2006-02-23 20:59 ` Alexander Skwar
2006-02-23 21:15 ` Qv6
2006-02-23 21:59 ` John Jolet
2006-02-23 22:35   ` Boyd Stephen Smith Jr.
2006-02-24  6:03   ` Alexander Skwar
2006-02-25  3:35     ` Zac Slade
2006-02-25  4:13       ` John Jolet [this message]
2006-02-25  4:32         ` Zac Slade
2006-02-25  5:14           ` John Jolet
2006-02-25  6:52             ` Alexander Skwar
2006-02-25  6:44         ` Alexander Skwar
2006-02-25  6:43       ` Alexander Skwar
2006-02-25 11:24         ` Holly Bostick
2006-02-25 12:21           ` Alexander Skwar
2006-02-25  7:55       ` Jarry
2006-02-25 10:26         ` Alexander Skwar
2006-02-25 10:44           ` Jarry
2006-02-25 11:11             ` Alexander Skwar
2006-02-25 15:01             ` [gentoo-user] [OT] " Boyd Stephen Smith Jr.
2006-02-27  6:48             ` [gentoo-user] " Dirk Heinrichs
2006-02-28  5:01               ` Zac Slade
2006-02-28  9:03                 ` Dirk Heinrichs
2006-02-28  9:23                   ` Zac Slade
2006-02-28  9:29                 ` Boyd Stephen Smith Jr.
2006-02-28 13:53                   ` Dirk Heinrichs
  -- strict thread matches above, loose matches on Subject: below --
2006-02-23 20:58 CR Little
2006-02-23 21:36 ` Boyd Stephen Smith Jr.
2006-02-23 21:41 CR Little
2006-02-23 23:29 CR Little
2006-02-23 23:57 ` Boyd Stephen Smith Jr.
2006-02-24 14:40 CR Little

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=5283AACA-DC0D-409D-A67A-0BCC9666AC14@jolet.net \
    --to=john@jolet.net \
    --cc=gentoo-user@lists.gentoo.org \
    /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