From: Phillip Susi <psusi@cfl.rr.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Avi Kivity <avi@redhat.com>
Subject: Re: [linux-lvm] Problems resizing physical volume
Date: Wed, 14 Apr 2010 10:47:43 -0400 [thread overview]
Message-ID: <4BC5D58F.2030809@cfl.rr.com> (raw)
In-Reply-To: <4BC58DF3.608@redhat.com>
On 4/14/2010 5:42 AM, Avi Kivity wrote:
> (resending, first try didn't seem to make it to the archives)
>
> Due to dracut creating huge initrds, I now need a larger /boot. So I'd
> like to reduce my lvm physical volume on the same disk in order to make
> room.
This doesn't directly address your issue, but I'd point out that if
/boot were itself an lv instead of a normal partition, resizing it would
be easy ;)
Personally I just leave /boot on the root lv.
> Looks like all extents are already allocated (that's the 'a', right?).
> But it claims that 10G are free! And sure, if I create a new volume,
> space is found at extent 4384:
The output is kind of silly in that it shows the free extents too
without any indication that they are free.
>> [root@violet-regb ~]# pvmove /dev/sda2:4704-4765 /dev/sda2:4384-4445
>> No extents available for allocation
>
> At this point I gave up. Is there any way to accomplish this?
pvmove normally is used to move segments off the pv to other pvs in
order to free up that pv for removal. So it is failing since it can not
find space on other disks, since you limited its search to specific
extents on the same disk. You need to add --alloc anywhere to stop it
from excluding the current disk from its search. The need for this is
kind of silly given that you explicitly tell it where to move to, it
should probably be assumed, but isn't.
next prev parent reply other threads:[~2010-04-14 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:42 [linux-lvm] Problems resizing physical volume Avi Kivity
2010-04-14 14:47 ` Phillip Susi [this message]
2010-04-14 14:59 ` Avi Kivity
2010-04-14 15:04 ` Avi Kivity
2010-04-14 15:14 ` Phillip Susi
2010-04-14 20:05 ` Stuart D. Gathman
2010-04-14 21:12 ` Phillip Susi
2010-04-14 21:28 ` Alasdair G Kergon
2010-04-14 21:57 ` Stuart D. Gathman
2010-04-14 22:27 ` Alasdair G Kergon
2010-04-24 1:39 ` Ron Johnson
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=4BC5D58F.2030809@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=avi@redhat.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).