All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Total free space using added VGs and LVs
Date: Sun, 25 Oct 2009 09:46:10 +0100	[thread overview]
Message-ID: <20091025084610.GA737@maude.comedia.it> (raw)
In-Reply-To: <29ae894c0910241004k327b0ff8w6577b83af3701753@mail.gmail.com>

On Sat, Oct 24, 2009 at 07:04:49PM +0200, brem belguebli wrote:
>It's non sense arguing that LVM is not intended for root due to the
>fact that you cannot shrink it  (growing online is operational and
>works fine).
>
>This is the only thing that is not allowed, though technically could
>it be possible.
>
Online shrinking is more difficult to achieve than online growing, and
is much less frequently needed, it usually happens due to bad planning.
I know some filesystem on different oses (namely vxfs) and btrfs on linux
allow online shrinking, ext3/4 and xfs don't.

The argument i find very difficult to grasp is what's so critical about
root filesystem versus other filesystems
If your server is (i.e.) a database server you will feel the filesystem
holding the database data is as critical as the root filesystem, if you
need to unmount that you might as well reboot. And the probability of
having to touch the data filesystem is much higher than that of having
to touch root.

Also the argument that the server is in a colo miles away is nonsense,
if it is a critical system it should have some means of oob management,
most server vendors offer those as standard components.

L.


-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  parent reply	other threads:[~2009-10-25  8:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 14:52 [linux-lvm] Total free space using added VGs and LVs Lou Arnold
2009-10-19 17:21 ` Stuart D. Gathman
2009-10-19 18:03 ` Drew
     [not found]   ` <a5a956f70910191114r3025ec45r5ddb2e02620fb0c0@mail.gmail.com>
2009-10-19 18:41     ` Drew
     [not found]       ` <a5a956f70910191200t340c02c2t28f14d3aef46cfdc@mail.gmail.com>
2009-10-19 19:51         ` Drew
2009-10-20  0:26           ` Lou Arnold
2009-10-20  3:19             ` Drew
     [not found]               ` <a5a956f70910201044j12e70c1cg78f454e580595815@mail.gmail.com>
2009-10-21 15:02                 ` Lou Arnold
2009-10-21 15:28                 ` Drew
2009-10-21 19:03                   ` Lou Arnold
2009-10-21 19:18                     ` Ryan Anderson
2009-10-23  0:26                       ` Lou Arnold
2009-10-23  0:52                         ` Stuart D. Gathman
2009-10-21 22:54                     ` David
2009-10-23  6:52                     ` Luca Berra
2009-10-23 19:06                       ` Lou Arnold
2009-10-23 20:12                         ` Ryan Anderson
2009-10-23 20:41                           ` Lou Arnold
2009-10-24  0:06                             ` Brian McCullough
2009-10-24  7:34                               ` Luca Berra
2009-10-24 16:43                               ` Lou Arnold
2009-10-24 17:04                                 ` brem belguebli
2009-10-24 19:16                                   ` Lou Arnold
2009-10-24 20:54                                     ` brem belguebli
2009-10-24 21:21                                       ` Lou Arnold
2009-10-24 22:04                                       ` Stuart D. Gathman
2009-10-25  8:46                                   ` Luca Berra [this message]
2009-10-25 13:13                                     ` Drew
2009-10-25 18:09                                       ` Stuart D. Gathman
2009-10-25 19:17                                         ` Stuart D. Gathman
2009-10-26 15:20                                           ` Lou Arnold
2009-10-26 19:39                                             ` Stuart D. Gathman

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=20091025084610.GA737@maude.comedia.it \
    --to=bluca@comedia.it \
    --cc=linux-lvm@redhat.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.