Dynamic Root Disk A.3.13 * Release Notes (766141-001, March 2014)

on LVM2 systems, and “drd sync”. The entries which were deleted pertain to volMgrVers,
syncDate, and creationDate. On LVM 2 systems, “drd mount” would produce the
following error:
* Mounting Inactive System Image ERROR:
Mounting the file system fails. - Mounting the inactive system
image fails. - The command "/usr/bin/sh -c
/var/opt/drd/tmp/drdq31CuWfbL/.drdvgimportcmd " fails with the
return code 1. The error message from the command is "vgimport:
Error: The major number for the group file "/dev/drd00/group"
corresponds to volume group version 1.0
With the fix, drd_unregister_mirror executes successfully.
• QXCR1001105660: Prior to the fix for this CR, when using ssh -x to a system, execution
of drd runcmd for a GUI application would result in an X11 forwarding failure as follows:
* Executing command: "/usr/sbin/swinstall"
NOTE: The interactive UI was invoked, since no software was
specified. Xlib: connection to "localhost:13.0" refused by server
Xlib: PuTTY X11 proxy: MIT-MAGIC-COOKIE-1 data did not match.
With this fix, the GUI now runs correctly.
• QXCR1001106819: Prior to this fix drd activate and drd deactivatewould attempt
to set the High Availability bootpath on vPar systems that do not support the High Availability
bootpath. With this fix drd activate and drd deactivate do not attempt to set the
High Availability bootpath on vPar systems.
• QXCR1001113284: Prior to this fix drd sync could not tolerate filenames that contain
unprintable control characters. With this fix drd sync now handles unprintable control
characters as well as characters in the extended ASCII code set.
Version A.3.8 (March 2011)
DRD version A.3.8 contains the following new features:
• Ability to sync file system and volume group information
• New FAQ entry on using DRD in a vPars environment
DRD version A.3.8 contains fixes for the following defects:
• QXCR1000968514: Prior to this fix, if a clone disk or original boot disk was removed from
a system, DRD commands would fail with confusing messages. This change clarifies the
messages and makes them consistent for roots managed by either LVM or VxVM.
• QXCR1001024172: Prior to this fix, drd would create a clone or mirror on an NPIV disk.
After the fix, drd rejects the target with an appropriate message that NPIV disks are not
bootable.
• QXCR1001026491: Prior to this fix, if boot disks were moved by using pvmove or by creating
and breaking mirrors without a reboot, drd clone would fail with the following errors:
ERROR: Making the file system bootable on clone fails.
- Mounting the file system fails.
- Mounting the inactive system image fails.
- The "mount" command fails with the return code "1". The error
message from the command is
"mount: /dev/drd00/lvol3 is already mounted on
/var/opt/drd/mnts/sysimage_001"
- Use the "bdf(1M)" and "umount(1M)" commands to remove any
conflicting mounts.
* Making New System Image Bootable failed with 1 error.
* Unmounting New System Image Clone
* System image: "sysimage_000" on disk "/dev/disk/disk15"
ERROR: Unmounting the file system fails.
- Unmounting the clone image fails.
- The volume "/dev/drd00/lvol3" is part of the inactive system image, but is mounted at
"/var/opt/drd/mnts/sysimage_001/" rather than under the directory
Version A.3.8 (March 2011) 9