Dynamic Root Disk A.3.13 * Release Notes (766141-001, March 2014)
ERROR: dump device 64:0x2 cannot be used and will be ignored:
device could not be opened
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 1, minor is 0xa27; start = 0, size = 744488960
In addition, on the booted clone, crashconf -v may also show incorrect entries in the persistent
dump device list similar to the following:
...
Persistent dump device list:
64:0x2
...
Workaround
This issue can be worked around by switching modes from config_crashconf_mode to
config_deprecated_mode using crashconf –o on the original system, prior to cloning. Any
dedicated dump devices will also need to be added to fstab prior to cloning.
Status: A fix will be available in a future DRD release. (QXCR1001101295)
Whole disk layout limitation
Issue
DRD clone fails when trying to clone a booted system with Whole Disk layout
While Ignite-UX does supports the Whole Disk layout, which has everything configured in the root
(“/”) volume, DRD does not support the cloning of such a configuration. DRD requires a volume
manager to clone the boot disk contents and since Whole disk layout does not have any volume
manager configured drd clone command fails. It is an expected behavior.
Here is the log seen while cloning such a configuration:
# drd clone -v -t /dev/disk/disk23
======= 10/01/12 12:16:09 IST BEGIN Clone System Image (user=root) (jobid=iuxonx6)
* Reading Current System Information
ERROR: System information retrieval fails.
- Gathering system configuration information fails with the following error(s):
- The command "/opt/drd/lbin/drd_save_config" fails with the return code 2. The error message from the command
is
"drd_save_config - running in drd context
drd_save_config: Error - disk not in the volume/disk group"
* Reading Current System Information failed with 1 error.
* DRD operation failed, contents of /var/opt/drd/tmp copied to /var/opt/drd/save.
======= 10/01/12 12:16:15 IST END Clone System Image
failed with 1 error. (user=root) (jobid=iuxonx6)
Workaround
There is no resolution to this case. DRD does not supports Whole disk layout.
Cloning with VxVM volumes having special characters
Issue
DRD clone fails when VxVM volume names have special characters
While Ignite-UX does supports VxVM volume names with special characters in it, DRD does not
support cloning of such a configuration. It is an expected behavior. Here is the ERROR message
seen while cloning such a configuration:
ERROR: Clone file system creation fails.
- Creating the target file systems fails.
- Start of output from /usr/lib/vxvm/bin/vxrootmir:
- VxVM vxrootmir INFO V-5-2-2501 14:36: Gathering information on the
current VxVM root configuration
Whole disk layout limitation 19