From: Lou Arnold <larnolda1@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Total free space using added VGs and LVs
Date: Sat, 24 Oct 2009 14:21:12 -0700 [thread overview]
Message-ID: <a5a956f70910241421h195cf525m59c262ba8c90aeb2@mail.gmail.com> (raw)
In-Reply-To: <29ae894c0910241354k67768707je61a9d25d3c14f6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5481 bytes --]
Brem,
I agree. I thought it should be possible. Perhaps someone else can try it
and let us know in a future blog. I just don't have enough experience to
take it farther.
Regards,
Lou.
On Sat, Oct 24, 2009 at 1:54 PM, brem belguebli <brem.belguebli@gmail.com>wrote:
> Hi Lou,
>
> Who is talking about unmounting root ?
>
> I'm just saying shrinking should be possible online as long as some
> conditions are met (FS usage less than X %, reduced fragmentation ...)
>
> Of course, this kind of procedure requiring a max of caution because
> of the high risk of data loss, I'm not sure it'll get implemented in
> the current tools.
>
>
>
> 2009/10/24, Lou Arnold <larnolda1@gmail.com>:
> > Hahaha. Brem, you and I think alike. If you can do it let me know. I
> don't
> > think people can think of a way to keep the system on-line and yet
> dismount
> > root so that LVM commands can work on it. If you can make it work, I'll
> buy
> > you a virtual beer.
> > Regards,
> > Lou.
> >
> > On Sat, Oct 24, 2009 at 10:04 AM, brem belguebli
> > <brem.belguebli@gmail.com>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.
> >>
> >>
> >>
> >> 2009/10/24, Lou Arnold <larnolda1@gmail.com>:
> >> > Haha, Yes, it would have been nice for someone to have told me about
> >> LVM and
> >> > root. It would have saved literally days of time. But my work is
> >> > experimental and never with production system. In any case, now I know
> >> > better.
> >> >
> >> > As for the LiveCD suggestion, I did not intend to discount it. I had
> in
> >> fact
> >> > tried it several times, but with some success. It probably just a
> >> > matter
> >> of
> >> > finger problems for the failures. But I truly expected a graceful
> >> > dismantling process without the need of shutting down the system.
> >> >
> >> > This was in fact a good experience. When you have to dig into things
> to
> >> > understand why something works or doesn't work, you are always luckier
> >> than
> >> > if things go perfectly right from the beginning.
> >> >
> >> > Thanks to everyone for your help.
> >> > Lou.
> >> >
> >> >
> >> >
> >> > On Fri, Oct 23, 2009 at 5:06 PM, Brian McCullough <bdmc@bdmcc-us.com>
> >> wrote:
> >> >
> >> >> On Fri, Oct 23, 2009 at 01:41:23PM -0700, Lou Arnold wrote:
> >> >> > Ryan, Thanks for your suggestion. I know it works, but I had hoped
> to
> >> >> have a
> >> >> > solution that didn't stop the whole system while I fixed it.
> >> >> >
> >> >> > To Drew:
> >> >> > I think you were quite right when you spoke about planning the file
> >> >> system.
> >> >> > I've come to realize that my question is somewhat naive. One simply
> >> >> doesn't
> >> >> > do what I wanted to exactly because there is no easy way to
> dismantle
> >> >> > it.
> >> >> It
> >> >> > would be better to partition off some part of the OS drive and add
> >> that
> >> >> to a
> >> >> > new volume group (or a new logical volume group) and mount that
> under
> >> >> > "/mnt", and then add whatever partitions on new drives to that
> >> >> > logical
> >> >> > volume. That logical volume could be dismounted and worked on,
> >> >> > whereas
> >> >> > whatever is under root cannot be worked on easily.
> >> >>
> >> >>
> >> >> Lou,
> >> >>
> >> >> I'm surprised that you haven't yet been told that one of the first
> >> >> rules
> >> >> of
> >> >> LVM is "don't use it for root!" Actually, I don't really hold with
> >> that,
> >> >> but it is MUCH more important to plan what you are doing when you do
> >> have
> >> >> an
> >> >> LVM root partition. As you have found, you can not manipulate an LVM
> >> >> partition while it is mounted. ( I know, there are ways for certain
> >> types
> >> >> of
> >> >> filesystems, but in general, the rule holds. ) That is especially
> true
> >> >> when
> >> >> the partition that you want to manipulate is root ( / ).
> >> >>
> >> >> My general practice is to set up the following list of Logical
> Volumes
> >> >> (
> >> >> the minimum which serves for most general purpose machines ): root,
> >> swap,
> >> >> home, usr, var. I generally allocate somewhere around 1G for the
> root
> >> >> partition. The others are sized appropriately for the environment.
> >> That
> >> >> usually leaves me a lot of free space on modern drives for "data"
> >> >> space.
> >> >>
> >> >> The recommendation that you should find a LiveCD at this point is
> >> probably
> >> >> one that you should respect. Playing with mounted filesystems,
> >> >> particularly
> >> >> root, can rapidly lead you down a very nasty path.
> >> >>
> >> >>
> >> >> Brian
> >> >>
> >> >> _______________________________________________
> >> >> linux-lvm mailing list
> >> >> linux-lvm@redhat.com
> >> >> https://www.redhat.com/mailman/listinfo/linux-lvm
> >> >> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >> >>
> >> >
> >>
> >> _______________________________________________
> >> linux-lvm mailing list
> >> linux-lvm@redhat.com
> >> https://www.redhat.com/mailman/listinfo/linux-lvm
> >> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
[-- Attachment #2: Type: text/html, Size: 8048 bytes --]
next prev parent reply other threads:[~2009-10-24 21:21 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 [this message]
2009-10-24 22:04 ` Stuart D. Gathman
2009-10-25 8:46 ` Luca Berra
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=a5a956f70910241421h195cf525m59c262ba8c90aeb2@mail.gmail.com \
--to=larnolda1@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).