During backups, Symantec System Recovery Linux adds a disk signature in 4 bytes from offset 440 (0x1B8) on logical volumes of LVM.
|Article:TECH197041|||||Created: 2012-09-20|||||Updated: 2013-09-23|||||Article URL http://www.symantec.com/docs/TECH197041|
During backups, Symantec System Recovery Linux adds a disk signature in 4 bytes from offset 440 (0x1B8) on logical volumes of LVM (like /dev/vg/lv1) . Even if the backup job works successfully and the backed up disk has no problem, the applications that use logical volumes may terminate unexpectedly, fail to start, or report some volume errors.
SSRL never replaces the existing disk signature on the physical disks.
A command to view the current data in 4 bytes from offset 440 (0x1B8) on /dev/vg/lv1 is as follows.
# hexdump -s 4 -n 440 /dev/vg/lv1
Red Hat 5.x / 6.x / x64 / x86
The issue does not depend on the distribution, version or architecture.
When there is no data (zero-padding) in 4 bytes from offset 440 (0x1B8) on the detected logical volumes of LVM, SSRL adds the disk signature on them during backups.
In case of Symantec System Recovery Linux 2011, please apply Hotfix 1. This issue has been resolved by Hotfix 1.
In case of Symantec System Recovery Linux 2013, please apply Service Pack 1. This issue has been resolved by Service Pack 1.
SSRL adds the new disk signature on RAW disk even if backing up another volume. The RAW disk exists as logical disk on LVM.
Article URL http://www.symantec.com/docs/TECH197041