Dynamic Root Disk Frequently Asked Questions
drd runcmd swverify \*
top
2-8. Q:
Some processes in DRD, particularly drd clone and drd runcmd, take a significant
amount of time. Can these processes be interrupted?
A:
All DRD processes, including drd clone and drd runcmd, can be safely interrupted
issuing Control/C (SIGINT) from the controlling terminal or by issuing kill -
HUP<pid> (SIGHUP). This action causes DRD to abort processing and perform any
necessary clean up. Do not interrupt DRD using the kill -9 <pid> command
(SIGKILL), which fails to abort safely and does not perform cleanup.
top
3- Troubleshooting Dynamic Root Disk
3-1.
Why can't I see the inactive system image file systems when I run the bdf command?
3-2.
When I run DRD, what information should I collect before calling HP about a problem?
3-3.
I can't remember which disk was used as the target of my clone operation. How can I
identify it?
3-4.
I issued a drd activate command but changed my mind and do not want to boot the clone.
How can I undo the drd activate command
3-5.
Can I change file system sizes when I create a clone?
3-6.
How will fbackup|frecover handle “busy” files?
3-7.
What happens with the configuration scripts if I install patch A and later install patch B,
which then supersedes patch A?
3-8.
If I use the IgniteUX server; is it aware of the DRD clone?
3-1. Q:
Why can't I see the inactive system image file systems when I run the bdf
command?
A:
You have to mount the inactive system image before you can see the file systems using
bdf. Use the drd mount command to mount the inactive system image.
top
3-2. Q:
When I run DRD, what information should I collect before calling HP about a
problem?
A:
Before you contact HP, be sure to gather the following useful information:
• Find the HP-UX revision of your system by entering:
uname -a
• Look at the contents of the log files under /var/opt/drd. It may be helpful to
have the data for the entire session. In DRD log files, sessions are delineated
with ========. If there is too much data in the log, locate the first sign of
trouble and the next several error messages.)