From: "Michael T. Babcock" <mtb@mikebabcock.ca>
To: steve@myself.gen.nz,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] which files, which physical volumes?
Date: Sun, 26 Sep 2004 19:49:34 -0400 [thread overview]
Message-ID: <4157558E.7030409@mikebabcock.ca> (raw)
In-Reply-To: <4155EBA2.7020609@myself.gen.nz>
Steve Wray wrote:
> Well then its bogus; the physical volume I am trying to pvmove has a
> capacity of around 9G whereas the volume group of which it is a part
> has a nice 42G free.
>
> So how does that work out to not enough extents?
Does the Volume Group in question have 42GB of unallocated extents, or
42GB free on the allocated Logical Volumes?
If you had VG main with 60GB total containing LVs lv1 and lv2 each 20GB
then you'd have 2GB unallocated on the VG.
If you want more unallocated space on e.g. /dev/hdc1 (a member of VG
main) to move part of lv1 onto (from /dev/hda1), you'd have to do
something like:
resize_filesystem /dev/main/lv2 (down to smaller size)
lvresize -L (new size) /dev/main/lv2 # to resize the logical volume
using the space
pvmove -n /dev/main/lv2 /dev/hdc1 # to move as much as possible of lv2
off this PV
pvmove -n /dev/main/lv1 /dev/hda1 /dev/hdc1
Does that make sense to you?
--
Michael T. Babcock
next prev parent reply other threads:[~2004-09-26 23:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:29 [linux-lvm] which files, which physical volumes? Steve Wray
2004-09-24 6:17 ` Luca Berra
2004-09-24 6:31 ` Steve Wray
2004-09-25 16:20 ` Clint Byrum
2004-09-25 16:50 ` Alasdair G Kergon
2004-09-25 22:05 ` Steve Wray
2004-09-26 23:49 ` Michael T. Babcock [this message]
2004-09-26 20:27 ` Eric Hopper
2004-09-26 20:38 ` Steve Wray
2004-09-27 0:30 ` Alasdair G Kergon
2004-09-27 7:58 ` Steve Wray
2004-09-24 19:00 ` John Stoffel
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=4157558E.7030409@mikebabcock.ca \
--to=mtb@mikebabcock.ca \
--cc=linux-lvm@redhat.com \
--cc=steve@myself.gen.nz \
/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