Vgextend Not Extending

Robbot · 07-22-2017, 02:07 PM

Hello,

Sorry for the noob question on RHEL7.3. I have an sdc1 (5mb) partition that does not extend my volume group. I ran pvcreate on it, and it shows ok on pvs (psize and pfree match). However, when I vgextend VG /dev/sdc1, though it shows successful, it does not extend it at all. It still says 0 free space. The partition shows up when I run vgdisplay -v (though sdc1 shows Allocatable=no). I then removed it from VG and tried vgcreate NEWVG /dev/sdc1, and that works just fine. The same thing is happening to sdc2 and sdc3 partitions. Any idea as to what could be the issue here? Thanks.

smallpond · 07-22-2017, 02:29 PM

When you are using LVM there's not much reason to have multiple partitions on the disk. Make one partition sdc1 using the whole disk. Use parted or your favorite fdisk flavor and make one VG on it. Then make multiple LVs for the spaces that you need. Once created, it's hard to change partition sizes. That's why LVM is easier.

You need multiple partitions if you are booting multiple OS.

syg00 · 07-22-2017, 06:10 PM

LVM abstracts the partitioning - perfect use case in this case. Try a "vgscan -ay", or if that doesn't do the trick, use pvchange to make it allocatable.

Robbot · 07-30-2017, 01:34 PM

Thanks. It doesn't look like that worked though. I ran vgscan -y ( a was not recognized) before and after adding /dev/sdc1, but the VG still shows as 0 Free PE. I had tried the pvchange to make it allocatable before, but that also failed with the below error:

Allocatability not supported by orphan lvm2 format PV /dev/sdc1
Physical volume /dev/sdc1 not changed
0 physical volumes changed / 1 physical volume not changed

rknichols · 07-30-2017, 04:31 PM

Quote:

Originally Posted by syg00

Try a "vgscan -ay", or if that doesn't do the trick, use pvchange to make it allocatable.

Did you mean "vgchange -ay"?

syg00 · 07-30-2017, 08:30 PM

Oops, yep.
Sorry about that.

Jjanel · 08-06-2017, 06:57 PM

@OP: did you get it to work? How? Please note: it's important to bring closure, so others can benefit too!

Did you mean "sdc1 (5mb)"? Is 5mb too small (for lvm)? 1cyl? Or was it 5Gb?

http://www.linuxquestions.org/questi...ml#post5669556 (my fav LQhow2):

Quote:

Write for the future, simply because you are! Many years hence, someone may well encounter your post. Make your post a targeted information resource for them. ...

(therefore ...) Bring closure. "Your future footsteps-follower, many years hence," will only be frustrated by a cryptic follow-up of "I solved it." Having opened your can-of-worms, be sure to close it with a follow-up summary post detailing exactly what you did. And, mark the post as "[SOLVED]" to further identify it as a thread which bears a solution.

Best wishes! WELCOME to LQ! ENJOY your learning!

p.s. I wanna learn too!