SIOS TECHNOLOGY CORP.

LVM – Known Issues / Restrictions

Description
If you are using DataKeeper to protect LVM, the resource hierarchy cannot be modified automatically. See Volume Group Reconfiguration for details.
Important reminder about DataKeeper for Linux asynchronous mode in an LVM over DataKeepr configuration

Kernel panics may occur in configurations were LVM resources sit above multiple asynchronous mirrors. In these configurations data consistency may be an issue if a panic occurs. Therefore the required configurations are a single DataKeeper mirror or multiple synchronous DataKeeper mirrors.
Use of lkID incompatible with LVM overwritten on entire disk

When lkID is used to generate unique disk IDs on disks that are configured as LVM physical volumes, there is a conflict in the locations in which the lkID and LVM information is stored on the disk. This causes either the lkID or LVM information to be overwritten depending on the order in which lkID and pvcreate are used.

Workaround: When it is necessary to use lkID in conjunction with LVM, partition the disk and use the disk partition(s) as the LVM physical volume(s) rather than the entire disk.
A warning message about the file descriptor may be displayed

 File descriptor 3 (/dev/zero) leaked on lvchange invocation. Parent PID 123456: /etc/default/LifeKeeper-perl

When using LVM versions v2.03.24 through v2.03.30, multiple warning messages like the shown above may be output when operating lvmvg or lvmlv resources. These warnings are caused by a bug in the specified LVM versions and do not affect the operation of LifeKeeper. Therefore, you can safely ignore these warnings.
This issue is resolved by using LVM version v2.03.31 or later.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment
OSZAR »