From: Avi Kivity <avi@redhat.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Problems resizing physical volume
Date: Wed, 14 Apr 2010 12:42:11 +0300 [thread overview]
Message-ID: <4BC58DF3.608@redhat.com> (raw)
(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.
However, lvm doesn't want me to:
> lvm> pvs
> PV VG Fmt Attr PSize PFree
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G
Seems I have enough room.
> lvm> pvresize --setphysicalvolumesize 148.54G /dev/sda2
> /dev/sda2: cannot resize to 4753 extents as later ones are allocated.
> 0 physical volume(s) resized / 1 physical volume(s) not resized
So it seems lvm wants me to move the data around instead of doing it by
itself. What did I do (besides not reading the manual)?
Let's find a new home for the data:
> [root@violet-regb ~]# pvs --segments
> PV VG Fmt Attr PSize PFree Start SSize
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 0 480
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 480 192
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 672 320
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 992 320
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 1312 320
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 1632 2560
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 4192 128
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 4320 64
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 4384 320
> /dev/sda2 vg0 lvm2 a- 148.94G 10.00G 4704 62
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:
> [root@violet-regb ~]# lvcreate -L 1G -n new vg0
> Logical volume "new" created
> [root@violet-regb ~]# pvs --segments
> PV VG Fmt Attr PSize PFree Start SSize
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 0 480
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 480 192
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 672 320
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 992 320
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 1312 320
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 1632 2560
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 4192 128
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 4320 64
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 4384 32
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 4416 288
> /dev/sda2 vg0 lvm2 a- 148.94G 9.00G 4704 62
32 extents, 32MB each = 1GB. Let's move the 62 extents at the end manually:
> [root@violet-regb ~]# lvremove vg0/new
> Do you really want to remove active logical volume new? [y/n]: y
> Logical volume "new" successfully removed
> [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?
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2010-04-14 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:42 Avi Kivity [this message]
2010-04-14 14:47 ` [linux-lvm] Problems resizing physical volume Phillip Susi
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=4BC58DF3.608@redhat.com \
--to=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).