#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 August 2009 Update Release
# DynRootDisk v2 fileset revision B.1123.A.3.4.91
# DynRootDisk v3 fileset revision B.1131.A.3.4.91
# whatstring swm/drd: Revision:
# branches/DRD+SWM_0909_BRANCH/smd@78746
#
# This release can be downloaded from the web.
# For more information, see http://www.docs.hp.com/en/DRD/
#
QXCR1000945120: This fix resolves the following issue that
might be seen after updating from 11.23 to 11.31:
# drd status
======= 07/06/09 15:13:34 MDT BEGIN Displaying DRD Clone Image Information (user=root)
(jobid=smdtest5)
/usr/lib/dld.sl: Unresolved symbol: io_get_mapping (code) from /opt/drd/lib/libdrdcfg.1 Pid 24077
in trap loop, signal 11 Memory fault(coredump)
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 August 2009 Update Release
# DynRootDisk v2 fileset revision B.1123.A.3.4.39
# DynRootDisk v3 fileset revision B.1131.A.3.4.39
# whatstring swm/drd: Revision:
# branches/DRD+SWM_0909_BRANCH/smd@78280
#
# This release is part of the September 2009 oe release.
# For more information, see http://www.docs.hp.com/en/DRD/
#
QXCR1000593736: This fix resolves the following error that
might occur while cloning fully allocated VxVM root disks to
targets of the same size:
ERROR: Analysis of file system creation fails.
- Analysis of target fails.
- The following messages, including errors, were obtained during
analysis:
E:The total volume sizes in disk group: "drd_rootdg" exceed the
available capacity by 19Mb.
E:The disk capacity available is not sufficient to create the volume
"/var" with the size specified (disk space is short by 19Mb). Reduce
the size of this volume (or other volumes that share the same disk
group), or use additional/larger disks.
* Analyzing For System Image Cloning failed with 1 error.
QXCR1000910365: This fix resolves the following error that
can occur if a VxVM volume mountpoint is longer than
32 characters:
drd_save_config: Error - cannot determine usage of mounted
volume "/dev/vx/dsk/dg_dd0/lvol1".
QXCR1000897891: This fix resolves the following error that
can occur if a VxVM group name has more than 16 characters:
nbbak51#/>drd clone -v -x overwrite=true -t /dev/disk/disk571
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
VxVM vxdg ERROR V-5-1-582 Disk group backup51_archdg0: No
such disk group
ERROR: DESCRIBE_GROUP: Disk group "backup51_archdg0"
does not exist.
drd_save_config: Error - The attributes of the VxVM disk
group "backup51_archdg0" can not be determined."
QXCR1000920461: This fix resolves control script failures
that occur when the scripts call mkboot and other commands
that access the fsdaemon on the system. This is likely to
occur when installing boot loader patches on an 11.31
system. The fix is to start and stop a temporary fsdaemon
in the chrooted environment.
QXCR1000898663: This fix recreates the inventory files
that previously caused DRD to fail. Prior to this fix,
DRD failed to reconcile legacy paths in the inventory
files with the agile paths coming from QBOOT. This resolves
the following error:
ERROR: Retrieval of DRD registry data fails.
- Validating the DRD registry fails.
- The device special file "/dev/disk/disk5" cannot be identified in
the system configuration information.
QXCR1000875680: Prior to this fix, there was no check for
kernel compatibility while running DRD commands. The user
would possibly see a core dump or have the DRD command fail
unpredictably. With this fix, DRD screens which commands to
allow between an 11.23 active image and an 11.31 clone, or
vice-versa. If the two images have a different OS installed,
the following commands are not allowed: drd runcmd update-ux,
drd runcmd swinstall, drd runcmd swremove.
QXCR1000925798: The fix for QXCR1000925798 checks for
LVM 2.0-formatted disks and will not overwrite them unless
-x overwrite=true. In addition,if the disk is actually in
use by an LVM 2.0 bolume group, AND the version of LVM
is from September 2008 or later, DRD will not overwrite the
disk, even when -x overwrite=true.
However, DRD cannot recognize disks in use by LVM 2.0 when
the version of LVM is earlier than September 2008, and
will overwrite such disks if -x overwrite=true.
QXCR1000922936: Prior to the fix for QXCR1000922936, a
device special file for the EFI partition of the path to
the HPUX partition recorded in /stand/bootconf was not
always created. Subsequently, applications of patches to
the system that copied files to the EFI partition failed.
The fix for QXCR1000922936 ensures that the device file
recorded in bootconf has a corresponding EFI device file.
QXCR1000885757: This fix passes the root volume group to
drd_save_config and obtains usage and formatting
information without using detailed information about
logical volumes. As a result, un-necessary messages about
non-root volumes are not issued.
QXCR1000928707: Prior to the fix for QXCR1000928707, on a
system for where vxprint displays an invalid line for the
clone target with dmname set to "-", drd clone fails.
After the fix, the clone succeeds.
QXCR1000930813: Prior to the fix for QXCR1000930813, the
drd mount command vgimported an LVM clone with a single
path. After the fix, the clone group (usually drd00) is
vgextended to all paths.
QXCR1000924326: This fix resolves the following error that
can occur if swap or dump volumes in fstab use the
same placeholder mount point:
ERROR: Making the file system bootable on clone fails.
- Making clone image bootable fails.
- Merging source and clone fstab fails.
QXCR1000871723: On occasion, files that are actively
changing on the booted system cannot be copied to the
inactive image during a drd clone operation. Prior to
the fix for QXCR1000871723, drd was silent about the
missing files. After the fix for QXCR1000871723, drd
issues warning messages identifying the missing files,
and completes with a warning return code of 2.
QXCR1000905871: This fix introduces support for the
extended option "-x enforce_dsa=[true|false]" that can
be set to false to override DRD's determination of
whether a clone target or mirror is sufficiently large.
The default value of the option is true.
QXCR1000934473: Prior to the fix for QXCR1000934473, it
the clone target was listed in /stand/bootconf,
the message instructed the user to remove the device file
from bootconf and try again. The fix for
QXCR1000934473 amended the message to indicate that the
boot disk should not be used as a clone target.
QXCR1000932740: Prior to the fix for QXCR1000932740, a
complex merge of the fstab on the booted system was
done with the fstab created for the file systems in the
clone volume group. This resulted in a number
of errors in fstab. After the fix for QXCR1000932740,
the fstab is copied to the clone.
QXCR1000931471: Prior to the fix for QXCR1000931471, the
"drd clone -?" did not show the argument for the
"-t" option. The fix for QXCR1000931471 ensures the
argument is displayed.
QXCR1000857638: This fix resolves the following error
that might occur while running "drd activate" when a
multi-pathed 11.23 clone is mounted:
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: warning - /dev/vg00/swapfsvol has an umounted VxFS filesystem on it.
Therefore, any file system content in /dev/vg00/swapfsvol
will not be backed up.
drd_save_config: Error - The command "lvlnboot -v /dev/drd00" returned 1. If needed,
the command "vgscan -v " can be used to recreate the
"/etc/lvmtab" file. The lvlnboot error output is: Unable to query the I/O interface:
Parameter error. lvlnboot: Unable to print reliable
information.
QXCR1000893111: The fix enhances performance on systems
with large I/O configurations.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 January 2009 Update Release
# DynRootDisk v2 fileset revision B.1123.A.3.3.221
# DynRootDisk v3 fileset revision B.1131.A.3.3.221
# whatstring swm/drd: Revision:
# branches/DRD+SWM+SWA_0903_BRANCH/smd@76628
#
# This release can be downloaded from the web.
# For more information, see http://www.docs.hp.com/en/DRD/
#
QXCR1000576024: Prior to the fix for QXCR100057602, a
pre-existing DRD registry that contained disks not on
the system caused subsequent drd clone commands to fail.
The fix for QXCR100057602 repairs this defect.
QXCR1000813238: Prior to the fix for QXCR1000813238, some
systems on which a device had been configured as the primary
paging area forsubsequent boots (see the -s option for the
swapon (1M) command) incorrectly cloned this information,
resulting in no swap device being configured when the clone
was booted. The fix for QXCR1000813238 repairs this defect.
QXCR1000838752: Before this fix, the update_LVM_label
script failed during a drd clone with mirror disk when
more than one dump logical volume was configured. The
script has been changed to allow for multiple root, boot,
swap and dump logical volumes.
QXCR1000857528: Prior to the fix for QXCR1000857528, the
clone of a swap volume larger that 32Gig was truncated to
32Gig. After the fix, the size of the swap volume on the
clone is the same as that on the original system.
QXCR1000858268: Prior to the fix for this defect, copies
of vmunix on a DRD clone could be sparse (with blocks of
binary zeroes compressed out), and thus unbootable. After
the fix for this defect, all copies of vmunix on the clone
have binary blocks of zeroes expanded.
QXCR1000865690: Prior to the fix for QXCR1000865690, the
drd status command would sometimes report the wrong disk as
the booted disk in cases when the system had booted from a
mirror of the clone disk. The fix for QXCR1000865690
repairs this defect.
QXCR1000874407: Prior to the fix for QXCR1000874407, the
system inventory was collected twice for a drd clone
operation. The fix for QXCR1000874407 ensures that the
inventory is not collected more than once.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 September 2008 Update Release
# DynRootDisk v2 fileset revision B.1123.A.3.2.1962
# DynRootDisk v3 fileset revision B.1131.A.3.2.1962
# whatstring swm/drd: Revision: A.3.2.1.1962 DRD_0809_web
#
# This release can be downloaded from the web.
# For more information, see http://www.docs.hp.com/en/DRD/
#
QXCR1000822669: Before this fix, lvlnboot was used to
determine if a volume was used for swap or dump. The lvlnboot
command does not support LVM version 2.0. DRD has been
changed to not use lvlnboot if the version of the volume
group is 2.0.
QXCR1000826388: Before this fix, swap and dump entries in
/etc/fstab were not merged into the clone's /etc/fstab file.
DRD has been changed to merge the entries.
QXCR1000795986: The target disk and mirror disk must not
exist in /stand/bootconf. Before this fix DRD did not detect
the error condition until after the clone operation had
executed for a long time. With thsi fix, DRD detects the
condition earlier and issues a message instructing the user
to remove the entry from /stand/bootconf.
QXCR1000833918: Before this fix, the rehost status did not
display correctly on 80 column displays. The "drd status"
command has been changed to format the rehost status so that
it displays correctly on 80 column displays.
QXCR1000846131: Before this fix, the corequisite declaration
for the 11.23 DRD.DRD-RUN fileset was incorrect. The
corequisite has been changed to declare the latest 11.23
SW-DIST patch, PHCO_38149, and the 0803.1123 and newer
versions of SW-DIST as the corequisite. Either one will
satisfy the corequisite.
QXCR1000834767: A rare data corruption problem has been fixed.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 September 2008 Update Release
# DynRootDisk v2 fileset revision B.1123.A.3.2.1959
# DynRootDisk v2 fileset revision B.1131.A.3.2.1959
# whatstring swm/drd: Revision: A.3.2.1.1959 DRD+SWM_0809_IC326
#
QXCR1000593563: (JAGag49793)
Prior to the fix, When using drd clone on an 11.31 system
where the source disk has no legacy paths, drd_scan_hw_host
had problems listing the devices on the system and the clone
would fail. After the fix, drd_scan_hw_host successfully
scans the host.
QXCR1000593564: (JAGag49794)
Prior to the fix, When using drd clone on an 11.31 system
where the target disk has no legacy paths, drd clone failed
saying it couldn't find the DSF. After the fix, drd clone
successfully identifies and uses the target disk.
QXCR1000593641: (JAGag49876) IC069: DRD clone failed
with "device special file cannot be identified"
FIXED IN 0712
QXCR1000755624: The drd_save_config tool now correctly
handles cases when the type of a file system cannot be
determined by fstyp.
QXCR1000796876: Before this fix, DRD did not ignore
whitespace at the end of DSF entries in /stand/bootconf.
The DRD parsing of entries in /stand/bootconf has been
changed to ignore anywhitespace at the end of DSFs in the
file.
QXCR1000799394: Before this fix, vx_nospace messages were
displayed during drd clone even when sufficient space was
available. With the fix, these messages no longer occur.
QXCR1000805110: Before this fix, DRD failed to update to the
11.31 version in the OE when updating from 11.23. DRD's
revision string has been changed to be prefixed with the the
OE, i.e. B.1123 or B.1131. The 11.31 revision will always be
higher than the 11.23 revision that will result in 11.23
DRD updated to 11.31 DRD.
QXCR1000813661: Before this fix, if clone boot disk was
specified in the drd registry with a legacy DSF, drd status
incorrectly used "_p1" to specify the EFI partition. After
the fix, it uses "s1".
QXCR1000820475: Before this fix, drd clone sometimes failed
with debug stack trace messages after receiving signal 11.
Bad debugging statements incorrectly referenced a NULL
pointer. These debug statements have been removed from the
code.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 March 2008 Update Release
# DynRootDisk v2 and v3 fileset revision A.3.1.0.1468
# whatstring swm/drd: Revision: A.3.1.1.1468 DRD_0803_WEB2
#
QXCR1000774818: Prior to the fix for QXCR1000774818, when DRD
was installed with SW-DIST revision B.11.xx.0803.318 or later,
a workaround was needed to use drd runcmd to swinstall
software from a directory depot on the booted system. This
fix eliminates the need for the workaround.
QXCR1000593338: Prior to the fix for QXCR1000593338, booting
the clone disk boot reports ignorable warnings because the
root group might not appear first in /etc/lvmtab. After the fix
for QXCR1000593338, the root group entry is always first in
/etc/lvmtab.
QXCR1000782396: Prior to the fix for QXCR1000782396, if the
root group is not named "vg00", and the group "vg00" exists
on the system, and a volume in "vg00" is not mounted,
the option "-x ignore_unmounted_fs" must be set to true.
After the fix for QXCR1000782396, the option must be set
to true only if a volume in the root group is not mounted.
QXCR1000757894: Prior to the fix, on a large machine with
many disks/LUNs an attempted drd mount operation when
there is no clone might take several minutes to fail. After
the fix the failure in this situation will happen
immediately.
QXCR1000775541: Prior to the fix for QXCR1000775541, a
manual vgimport of drd00 followed by a drd umount command
could cause subsequent drd mount commands to fail. The
problem only occurred if the manual vgimport was issued
without a mapfile specification and one or more volumes
was not of the form "lvoln" where "n" was the volume
minor number. This problem is now resolved.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 February 2008 Update Release
# DynRootDisk v2 and v3 fileset revision A.3.1.0.1452
# whatstring swm/drd: Revision: A.3.1.0.1452 DRD_0803_WEB
#
QXCR1000593913/JAGag50190: Prior to the fix for
QXCR1000593913, during the VxVM 5.0 clone the irrelevant
message " W:The version keyword for the VxFS file system
"/home" is set to "7". This requires the Base-VxFS-50
bundle, which does not appear to be available for loading.
The assumptions are that it is part of an archive." might
appear. This message will no longer appear.
QXCR1000594080/JAGag50370: Prior to the fix for
QXCR1000594080, during startup, if a boot device could
not be identified, drd_scan_hw_host would write continuous
messages to a logfile, eventually filling up /var. This
issue has been resolved.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 December 2007 Update Release
# DynRootDisk v2 and v3 fileset revision A.3.0.0.1280
# whatstring swm/drd: Revision: A.3.0.0.1280 DRD_0712_web
#
QXCR1000593641: (JAGag49876) IC069: Prior to this fix, DRD
clone failed with "device special file cannot be identified"
when SAN LUNs were made unavailable through zoning. This
defect has been fixed.
QXCR1000741235: Prior to this fix, a message regarding
MAX_G_TO_VD_MAP was incorrectly issued. This problem has
been resolved.
JAGag32371: Prior to the fix, if a logical volume with a
filesystem exists that is part of the root volume group
but was not mounted, then the clone operation would create
the logical volume but not copy its contents. After the
fix we issue an error if such a volume exists and allow
the user to override the error with the
"ignore_unmounted_fs" command line option.
JAGag43830: Prior to this fix - If an extra swap volume has
been added to the booted system and that system cloned,
then the clone mounted and drd runcmd issued, drd will
unmount the mounted clone. After this fix - drd will no
longer unmount the mounted clone in the above situation.
QXCR1000593561: Prior to the fix for QXCR1000593561, DRD
issued a stack trace during the clone operation when a
non-target, non-source disk had no legacy path. After the
fix, the error is corrected.
QXCR1000739307: Prior to the fix for QXCR1000739307. a
DRD clone of an LVM root could not be mounted on system
with 15 or more LVM volume groups. After the fix, this
operation succeeds.
QXCR1000746478: Prior to the fix for QXCR1000746478?, the
boot of a DRD clone of a VxVM root showed the root file
system ("/") mounted at /dev/root. After the fix, the root
file system is correctly mounted at
/dev/vx/dsk/drd_rootdg/rootvol.
QXCR1000746695: Prior to the fix for QXCR1000746695, the
S900drd startup script on systems with large hardware
configurations could take excessively long to complete on
systems without a DRD clone. After the fix, the script
completes in a timely fashion.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 and v3 September 2007 Update Release
# DynRootDisk v2 and v3 fileset revision A.2.0.0.612
# whatstring swm/drd: Revision: A.2.0.0.612 DRD_0709_web
#
JAGag27853: Prior to the fix for JAGag27853, DRD would
autogenerate the /etc/fstab file on the clone and not copy
the /etc/fstab file on the booted system. Any comments in
the original /etc/fstab were not found on the clone. Now
the /etc/fstab file is copied to the clone with the name
/etc/fstab.%d%m%y%H%M%S (date and time copy was made) so
the comments are available.
JAGag37192: Prior to JAGag37192, a locally mounted volume
that was not in vg00 and not in /etc/fstab was incorrectly
copied to the clone by the drd clone command. If the volume
was sufficiently large, the clone failed due to a lack of
disk space. The fix for JAGag37192 suppressed the copying of
these file systems and created mount points for them on the
clone.
JAGag38428: Prior to the fix for JAGag38428, the
options -x logfile, -x log_verbosity, and -x preview,
and -x verbosity were not supported for drd deactivate.
JAGag40139: Prior to the fix for JAGag40139, if the
/stand/bootconf file contained a different path to
the boot disk than the one shown by vgdisplay during a
clone, subsequent drd commands, such as mount, runcmd,
and activate, might have failed.
JAGag40141: Prior to the fix for JAGag40141, when using
drd_register_mirror to register a clone mirror, the parameter
was not checked to see if it was a valid device special file.
JAGag40311: Prior to the fix for JAGag40311, DRD clone failed
when a swap logical volume in a non-root volume group used
the placeholder mount point "/" in /etc/fstab.
JAGag40971: Prior to the fix for JAGag40971, When
-x overwrite=true was specified, DRD sometimes attempted to
use a disk that had an alternate path in use by a volume
group or disk group on the system.
JAGag41574: Prior to the fix for JAGag41574, the lif area
of the mirror of a DRD clone on a PA system was missing the
AUTO file. If the mirror was booted, the boot would stop
when the AUTO file was needed. The administrator would
then need to enter the contents of the AUTO file, such as
"hpux" or "hpux -lq". With the fix for JAGag41574 applied,
the AUTO file is correctly written to the lif area of the
mirror of the clone.
JAGag42903: Prior to the fix for JAGag42903, optimized DRD
executable would core dump when cloning a system that had
extra swap volumes added or lofs file systems mounted.
JAGag43578: This release includes a fix for JAGag43578 - an
issue with modifying system parameters was resolved in
response to HPSBUX02249.
JAGag46613: Prior to the fix for JAGag46613 (but after
A.2.0.0.592) save-config failed on any system with an
inactive volume group.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 June 2007 Update Release
# DynRootDisk fileset revision A.1.1.0.344
# whatstring swm/drd: Revision: A.1.1.0.344, DRD+SWA_0706_top
#
JAGag27435: The gathering of system information is time
consuming for large configurations and not needed for the
commands drd mount, drd umount and drd runcmd. JAGag27435
eliminates this un-needed overhead.
JAGag27441: The mechanism for updating the drd unsafe patch
list has been implemented and documented at
http://docs.hp.com/en/DRD/infolib JAGag27441 tracks this
change.
JAGag28315: The version of the drd unsafe patch list used
with drd runcmd swinstall/swremove is now displayed.
JAGag29554: The list of filesystems in drd00, determined
from /etc/fstab on the inactive image, is now sorted prior
to mounting.
JAGag30140: The drd clone operation failed with a parsing
error on any system with VxVM activated but with no diskgroup
defined. JAGag30140 eliminates the need for a diskgroup to be
defined.
JAGag30396: drd runcmd no longer starts swagentd for commands
that don't need a swagentd (swlist, swmodify, view).
JAGag31522: Reinstalling DRD without FileSystemsWeb caused
the message "ln: /opt/drd/lbin/disklist exists" to appear
in /var/adm/sw/swagent.log. JAGag31522 eliminates this
message.
JAGag32708: The commands drd mount, drd umount, drd runcmd,
and drd activate have been enhanced by JAGag32708 to fail
quickly if no clone exists.
JAGag32781: Updated all drd functions that operate on a clone
(mount, umount, runcmd, activate) to abort if the registry is
not valid.
JAGag34317: The first time an HP-UX system was booted after
DRD was installed, a vgcfgbackup syntax error message was
displayed in the rc.log. JAGag34317 eliminates the incorrect
and unnecessary invocation of the command vgcfgbackup.
JAGag35450: After hitting cntl-C during a clone process a
warning appeared on the screen saying that not all
filesystems had been unmounted. Attempting to reissue the
clone command resulted in an error message saying that the
drd00 volume was still mounted. Now Cntl-C during a clone
works properly and does not generate unnecessary error
messages.
#############################################################
# Dynamic Root Disk defects fixed in
# HP-UX 11i v2 Feb 2007 Web Release
# DynRootDisk fileset revision A.1.0.18.245
# whatstring swm/drd: Revision: A.1.0.18.245, DRD_0702_LR
#
JAGag28217: When any file system in vg00 was mounted under a
file system other than root (/), the unmounts of the file
system at the end of the drd clone operation, at the end of
drd runcmd operation, and during the drd umount operation
failed. JAGag28217 eleminates this issue and allows unmount
to work properly with these drd operations.