From: Brian McCullough <bdmc@bdmcc-us.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [LINUX-LVM] shrinking a volume inside an LVM
Date: Sat, 5 Jan 2008 01:35:26 -0500 [thread overview]
Message-ID: <20080105063526.GA19245@bdmcc-us.com> (raw)
In-Reply-To: <F61B3F3722111146AF452DF29FDCCF5F038D1BD8@xchg03.bolivar.k12.mo.us>
On Fri, Jan 04, 2008 at 02:50:00PM -0600, Kemp, Levi wrote:
> Most of this makes sense. Especially the part about using a live CD. But if you don't mind I'm gonna pick your brain on the other parts because I like to understand a command before I use it, so I can blame myself when I mess up ;-)
> Actually the only part I'm unsure about is 9-11. resize2fs will resize my ext2/3 file system which will clear up more room in my lvm to create another lv correct? Or do you have to shrink the file system then the lv to have the space back? I'm going to back up anything that I need to be safe, but I'd like to avoid a total reinstall right now(that's for May). Thanks again. I think you've got me on track. One more quick one, on 9 you said "amount occupied + some" wouldn't it be minus some?
Stuart answered at least as well as I could, but for the last, "occupied
+ some" is what I meant. By "occupied" I am talking about the amount of
data that actually exists in your "/" volume. Then, since you need a
little room to grow, add some to that value, so that you have a bit of
free space in that volume. ( As well as Stuart's explanation, to leave
room for errors. )
Brian
prev parent reply other threads:[~2008-01-05 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F61B3F3722111146AF452DF29FDCCF5F038D1BD3@xchg03.bolivar.k12.mo.us>
2008-01-04 19:07 ` [LINUX-LVM] shrinking a volume inside an LVM Kemp, Levi
2008-01-04 19:38 ` Brian McCullough
2008-01-04 20:50 ` Kemp, Levi
2008-01-04 20:59 ` Stuart D. Gathman
2008-01-04 21:58 ` Kemp, Levi
2008-01-05 6:37 ` Brian McCullough
2008-01-05 6:35 ` Brian McCullough [this message]
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=20080105063526.GA19245@bdmcc-us.com \
--to=bdmc@bdmcc-us.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 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.