Dynamic Root Disk Failure

[UNIX Engr]

Hello all,
I downloaded and installed DRD on my brand new 11.23 Itanium server. The server is fully patched and has nothing running on it yet.
When I run the command everything seems to work up to the point it begins to unmount the DRD lvols:

root@dnux048: /roots # drd clone -t /dev/dsk/c3t0d0

======= 02/06/07 12:51:35 MST BEGIN Clone System Image (user=root)
(jobid=dnux048)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning
* Creating New File Systems
* Copying File Systems To New System Image
* Making New System Image Bootable
* Unmounting New System Image Clone
ERROR: Unmounting the file system fails.
- Unmounting the clone image fails.
- The command "/usr/bin/sh -c
/var/opt/drd/tmp/drdXTH5dGVL/.drdvgchangecmd " fails with the return
code 16. The error message from the command is "vgchange: Couldn't
deactivate volume group "drd00":
Device busy
"
* Unmounting New System Image Clone failed with 1 error.

======= 02/06/07 13:27:23 MST END Clone System Image failed with 1 error.
(user=root) (jobid=dnux048)

A bdf before the run:
root@dnux004: /roots # bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 581632 316088 263520 55% /
/dev/vg00/lvol1 360448 144440 214416 40% /stand
/dev/vg00/lvol12 4710400 2019032 2670416 43% /var
/dev/vg00/lvol10 1024000 20495 943277 2% /var/tmp
/dev/vg00/lvol9 4710400 17625 4399484 0% /var/adm/crash
/dev/vg00/lvol11 6348800 2640848 3679024 42% /usr
/dev/vg00/lvol8 204800 8800 194528 4% /tmp
/dev/vg00/lvol7 262144 25899 221513 10% /roots
/dev/vg00/lvol6 1024000 37023 925319 4% /patches
/dev/vg00/lvol5 6660096 3751112 2886304 57% /opt
/dev/vg00/lvol4 262144 9296 250880 4% /home

A BDF after the run:
root@dnux004: /roots # bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 581632 316088 263520 55% /
/dev/vg00/lvol1 360448 144440 214416 40% /stand
/dev/vg00/lvol12 4710400 2019032 2670416 43% /var
/dev/vg00/lvol10 1024000 20495 943277 2% /var/tmp
/dev/vg00/lvol9 4710400 17625 4399484 0% /var/adm/crash
/dev/vg00/lvol11 6348800 2640848 3679024 42% /usr
/dev/vg00/lvol8 204800 8800 194528 4% /tmp
/dev/vg00/lvol7 262144 25899 221513 10% /roots
/dev/vg00/lvol6 1024000 37023 925319 4% /patches
/dev/vg00/lvol5 6660096 3751112 2886304 57% /opt
/dev/vg00/lvol4 262144 9296 250880 4% /home
/dev/drd00/lvol3 4710400 2019032 2670416 43% /var/opt/drd/mnts/sysimage_001
/dev/drd00/lvol12 4710400 2019032 2670416 43% /var/opt/drd/mnts/sysimage_001/var

Now I can manually unmount the DRD mount points, and I can use the newly created DRD disk to boot from, yet every time I run the command (I have tried it three times on two different Itanium servers) it hangs in basically the same place: always trying to unmount the /var file systems.

Anyone else experience this?
Any thoughts on what may be causing this?

Thanks!
Steve

[James R. Ferguson]

Hi Steve:

To begin, I have no experience with this product.

It would be interesting to see what files might be open on the DRD mountpoints and by what processes. I'd use 'lsof' to probe this.

Given that you say you can manually unmount the filesystems, I suspect that you are not going to find any open files or processes using these filesystems, though.

Regards!

...JRF...

[Judy Wathen · Accepted solution]

You are seeing a bug in the clone unmount that occurs when you have a file system mounted under another mount point. This defect will be fixed in the next release.

As a workaround until the defect is fixed, you can issue the â drd umount" command whenever you get the unmount failure. Since /var/adm/crash and /var/tmp will have been unmounted by the first attempt, the next unmount will succeed. You will need to do this after unmount failures in the "drd clone" "drd umount" and "drd runcmd" commands.

[UNIX Engr]

Thanks for the info!
I have scripted a work around by executing a "drd umount" commnad after the "drd clone" command.

Cheers!
Steve

[Judy Wathen]

Steve -

Just wanted to let you know that a new release of DRD that contains a fix to this defect is now available from HP's software depot. You can download Release A.1.0.18.245, issued in February 2007, by going to the Downloads and Patches section of the DRD documentation site:
http://docs.hp.com/en/DRD/

Thanks,
Judy