pvdisplay -v , vgdisplay -v, lvdisplay -v, vgscan -v (vg database aktualisieren), lvscan -v, pvscan -v
Mögliche Ursachen:
Haben Sie beim anlegen der Partition mit fdisk(8) die Id der Partition auf 0x8e gesetzt?
(Ältere Version von LVM haben die Id 0xfe verwendet).
Eventuell meldet pvcreate(8), dass das PV bereits initalisiert wurde. Sie können die Operation erzwingen, indem Sie die Option "pvcreate -f[f] ..." verwenden. (Vorsicht: Verwenden Sie dies nicht bei einem Physikal Volume, dass zu einer anderen Volume Group gehört!)
Your volume group is full or you've already reached the maximum logical volume size in that volume group. Logical volume size is limited by the size of the physical extents times their maximum amount, which only can be set at volume group creation time.
The default physical extent size is 4MB which limits ;-) logical volumes to a maximum of 256 Gigabyte (see vgcreate(8), vgdisplay(8)). If your volume group isn't full or you didn't reach the current logical volume size limit, your logical volume may have striped or contiguous allocation policy. Have a look at the physical volumes with vgdisplay or pvdisplay(8) to figure out, if there are not enough free (contiguous) physical extents.
Look at the free space on all destination disks you want to use (or which are implicit used) AND at the attributes of the logical volumes to be moved.
You can't move a contiguous logical volume when there isn't enough free contiguous space on any destination disk. In this case you can think about changing from contiguous allocation policy to next free and do the attribute change with lvchange(8).
You can't move a striped logical volume either, if there isn't enough space for the complete stripe on any destination physical volume. You can't move to physical volumes which are NOT allocatable. Think about changing this with pvchange(8).
Volume Groups und/oder Logische Volumes müssen vor dem Umbennen deaktiviert werden. (siehe auch lvrename(8), vgrename(8)).
Bring your system back online and look at the volume group backup files in /etc/lvmconf. There's at least one called /etc/lvmconf/VolumeGroupName.conf and possible more in the backup history called /etc/lvmconf/VolumeGroupName.conf.*.old. You can use these backup files to bring the configuration back to the one before the crash (see vgcfgrestore(8)).
This is NO absolute limit but it depends on the physical extent size you configured at volume group creation time. Please use option -s of the vgcreate command to give a larger physical extent size. For example with a physical extent size of 524288 KB (512 MB) you are able to map a logical volume of 32 Terabyte. Remember that current Linux kernels are limited to 1 Terabyte.
(Why can't i split my volume group my_vg? ) The physical volumes you want to split of into another volume group may NOT have logical extents of logical volumes staying in the original volume group you started with. Please use pvmove to seperate the logical volumes.
(Why can't i merge my two volume groups my_vg1 and my_vg2? )
A merged volume group can't go beyond the physical or logical volume limits of the destination volume group. This means for eg. that you can't merge my_vg1 with 20 logical volumes and my_vg2 with 30 logical volumes getting my_vg1, if my_vg1 has a 31 logical volume limit. You are only able to merge (up to now) volume groups with equal physical extent sizes.
(How can i move parts of my logical volume with very intensive i/o to a different physical volume? ) Please look at pvmove(8) and use the logical extent syntax to do the job.
... es handelt sich aber erst um mein 211tes Logisches Volume. Was ist das Problem?
Das Maximum von 256 Logischen Volumes (LV) bezieht sich auf die LVs aller Volume Groups (VG). Sie müssen also eventuell LVs in anderen VGs löschen, bevor Sie ihr neue LV anlegen können.