* [linux-lvm] Insufficient suitable allocatable extents for logical volume
@ 2011-04-24 16:09 Ron Johnson
2011-07-08 16:32 ` Paweł Brodacki
0 siblings, 1 reply; 2+ messages in thread
From: Ron Johnson @ 2011-04-24 16:09 UTC (permalink / raw)
To: LVM general discussion and development
Why does this happen? I think it has something to do with the fact that
I set the lv to striped.
TIA,
Ron
# lvm version
LVM version: 2.02.54(1) (2009-10-26)
Library version: 1.02.39 (2009-10-26)
Driver version: 4.17.0
(Yes, I know it's old. Blame Ubuntu)
# vgdisplay data_vg
--- Volume group ---
VG Name data_vg
System ID
Format lvm2
Metadata Areas 12
Metadata Sequence No 6
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 12
Act PV 12
VG Size 5.46 TiB
PE Size 8.00 MiB
Total PE 715392
Alloc PE / Size 476928 / 3.64 TiB
Free PE / Size 238464 / 1.82 TiB
VG UUID NPgp1H-6kkG-c4wL-KNyT-AVoh-Frlb-4nvfiT
# lvextend -v -l+100%FREE data_vg/data_lv
Finding volume group data_vg
Using stripesize of last segment 8.00 MiB
Archiving volume group "data_vg" metadata (seqno 6).
Extending logical volume data_lv to 5.46 TiB
Insufficient suitable allocatable extents for logical volume data_lv:
238464 more required
# lvextend -v -l+50%FREE data_vg/data_lv
Finding volume group data_vg
Using stripesize of last segment 8.00 MiB
Archiving volume group "data_vg" metadata (seqno 6).
Extending logical volume data_lv to 4.55 TiB
Insufficient suitable allocatable extents for logical volume data_lv:
119232 more required
# lvextend -v -l+10%FREE data_vg/data_lv
Finding volume group data_vg
Using stripesize of last segment 8.00 MiB
Rounding size (500774 extents) down to stripe boundary size for
segment (500768 extents)
Archiving volume group "data_vg" metadata (seqno 6).
Extending logical volume data_lv to 3.82 TiB
Insufficient suitable allocatable extents for logical volume data_lv:
23840 more required
--
"Neither the wisest constitution nor the wisest laws will secure
the liberty and happiness of a people whose manners are universally
corrupt."
Samuel Adams, essay in The Public Advertiser, 1749
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-lvm] Insufficient suitable allocatable extents for logical volume
2011-04-24 16:09 [linux-lvm] Insufficient suitable allocatable extents for logical volume Ron Johnson
@ 2011-07-08 16:32 ` Paweł Brodacki
0 siblings, 0 replies; 2+ messages in thread
From: Paweł Brodacki @ 2011-07-08 16:32 UTC (permalink / raw)
To: LVM general discussion and development
2011/4/24 Ron Johnson <ron.l.johnson@cox.net>:
> Why does this happen? I think it has something to do with the fact that I
> set the lv to striped.
>
> TIA,
> Ron
From Red Hat's LVM Administrator's Guide:
"Striped logical volumes can be extended by concatenating another set
of devices onto the end of
the first set. In order extend a striped logical volume, however,
there must be enough free space on
the underlying physical volumes that make up the volume group to
support the stripe. For example,
if you have a two-way stripe that uses up an entire volume group,
adding a single physical volume
to the volume group will not enable you to extend the stripe. Instead,
you must add at least two
physical volumes to the volume group."
So yes, the fact that you set the LV to stripped matters. Read the
manual http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/pdf/Logical_Volume_Manager_Administration/Red_Hat_Enterprise_Linux-6-Logical_Volume_Manager_Administration-en-US.pdf,
it contains a section on extending striped logical volumes.
Regards,
Paweł
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-07-08 16:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-24 16:09 [linux-lvm] Insufficient suitable allocatable extents for logical volume Ron Johnson
2011-07-08 16:32 ` Paweł Brodacki
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).