LV Larger than DIsk?
I was trying to get 2.5.47 going this weekend, some of you may have seen in the chan.
I finally got all the patches and got them applied for all the bits broken in that kernel. I got compiled and booted, but...
After compiling lvm2 tools, vgscan runs fine, but then vgchange -ay only activates 2 of the 5 lv's. I get an error that the LV is too large for the allocated PE.
I've got 2 PVs, one with 3 partitions, then the rest part of the /dev/Data volume, and another disk I just added that I simply did lvextend to one of the LV's I wanted to increase the size of.
Under LVM1, all is well, under LVM2, I'm having some serious issues. Please advise.
Signature · 2 lines
Austin Gonyou <[email protected]> Coremetrics, Inc.
Quoted 3 lines · Austin Gonyou
After compiling lvm2 tools, vgscan runs fine, but then vgchange -ay only activates 2 of the 5 lv's. I get an error that the LV is too large for the allocated PE.
So I can investigate this, please quote the *specific* output you are seeing when you get the error. Also the version numbers e.g. type:
lvm version
Please maybe also retry with Beta4 released today and see whether or not the problem is still there.
Quoted 3 lines
I've got 2 PVs, one with 3 partitions, then the rest part of the
/dev/Datavolume, and another disk I just added that I simply did lvextend to one of the LV's I wanted to increase the size of.
Please also send a copy of the relevant metadata backup/archive files under /etc/lvm - one from the backup directory (or by running vgcfgbackup) showing the current metadata, and one from the archive directory showing the metadata before you made any changes to it.
[You can send these to me directly or post a URL, if you prefer not to send them to everyone on the list.]
Alasdair
Signature · 1 line
[email protected]