| |
| 7.7.1.1. Q: | Q: Why can't I see the inactive system image file systems when
I run the bdf command? |
| A: | 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. |
| 7.7.1.2. Q: | Q: I can't remember which disk was used as the target of my
clone operation. How can I identify it? |
| A: | A: Use the drd status command. |
| 7.7.1.3. Q: | Q: 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? |
| A: | A: If you run drd activate and then decide
not to boot the inactive image on the next reboot, use the drd deactivate command to set the primary boot disk to
the currently booted disk. For further information on the drd deactivate command, see The drd deactivate Command and the drd-deactivate(1M) manpage. |
| 7.7.1.4. Q: | Q: Can I change file system sizes when I create a clone? |
| A: | A: This release of DRD does not provide a mechanism for resizing
file systems during a drd clone operation. However,
after the clone is created, you can manually change file system sizes
on the inactive system without needing an immediate reboot. The Using the Dynamic Root Disk Toolset white paper describes
resizing file systems other than /stand. The Using the DRD toolset to extend the /stand file system in an LVM
environment white paper describes resizing the boot (/stand) file system on an inactive system image. You can
access these white papers at: http://docs.hp.com/en/oshpux11iv2.html#Dynamic%20Root%20Disk. |
Printable version
