unable to create DRD clone after reinstall

[S. Ney]

Hello, I have an hpux 11.23 rx6600 itanium system. I recently removed and re-installed drd on the system due to earlier errors in trying to create an updated clone disk and mirror. I currently have:
B.1123.A.3.3.221 Dynamic Root Disk installed.

I am getting the following errors:
- Start of errors written by /opt/drd/lbin/drdconfigure:
- * Using LVM for disk 0/4/1/0.0.0.1.0 (c0t1d0s2), group:
drd00
* Creating LVM physical volume "/dev/rdsk/c0t1d0s2"
(0/4/1/0.0.0.1.0).
* Creating volume group "drd00".
ERROR: Command "/sbin/vgcreate -A n -e 4356 -l 255 -p 16 -s 32
/dev/drd00 /dev/dsk/c0t1d0s2" failed.

- End of errors written by /opt/drd/lbin/drdconfigure
- Command "/opt/drd/lbin/drdconfigure" fails with the return code 255.
The entire output from the command is given below:
- Start of output from /opt/drd/lbin/drdconfigure:
- Physical volume "/dev/rdsk/c0t1d0s2" has been successfully created.
vgcreate: Volume group "/dev/drd00" could not be created:
A volume group is already using this major and minor number.
Please check the minor number of the "group" device file.

- End of output from /opt/drd/lbin/drdconfigure
* Creating New File Systems failed with 1 error.
* Unmounting New System Image Clone
* System image: "sysimage_001" on disk "/dev/dsk/c0t1d0"
* Cleaning up after clone errors.

======= 09/28/09 00:34:39 EDT END Clone System Image failed with 1 error.
(user=root) (jobid=avenger)


======= 09/28/09 00:36:15 EDT BEGIN Clone System Image Preview (user=root)
(jobid=avenger)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
* The disk "/dev/dsk/c1t3d0" contains data which will be overwritten.
* The disk "/dev/dsk/c0t1d0" contains data which will be overwritten.
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning

======= 09/28/09 00:36:31 EDT END Clone System Image Preview succeeded.
(user=root) (jobid=avenger)


======= 09/28/09 00:36:54 EDT BEGIN Clone System Image (user=root)
(jobid=avenger)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
* The disk "/dev/dsk/c1t3d0" contains data which will be overwritten.
* The disk "/dev/dsk/c0t1d0" contains data which will be overwritten.
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning
* Creating New File Systems
ERROR: Clone file system creation fails.
- Creating the target file systems fails.
- Command "/opt/drd/lbin/drdconfigure" fails with the return code 255.

I've tried the command on two different disks and am getting the same error:
ERROR: Command "/sbin/vgcreate -A n -e 4356 -l 255 -p 16 -s 32 /dev/drd00
/dev/dsk/c0t1d0s2" failed.
* Using LVM for disk 0/4/2/0.0.0.3.0 (c1t3d0s2), group: drd00
* Creating LVM physical volume "/dev/rdsk/c1t3d0s2" (0/4/2/0.0.0.3.0).
Physical volume "/dev/rdsk/c1t3d0s2" has been successfully created.
* Creating volume group "drd00".
vgcreate: Volume group "/dev/drd00" could not be created:
A volume group is already using this major and minor number.
Please check the minor number of the "group" device file.

ERROR: Command "/sbin/vgcreate -A n -e 4356 -l 255 -p 16 -s 32 /dev/drd00
/dev/dsk/c1t3d0s2" failed.
root@avenger:/var/opt/drd>
I've checked my /dev/ for duplicate minor numbers but don't see any duplicates.
root@avenger:/var/opt/drd> ll /dev/*/group
crw-r----- 1 root sys 64 0x000000 Sep 18 12:49 /dev/vg00/group
crw-r----- 1 root sys 64 0x010000 Sep 23 09:43 /dev/vg01/group
root@avenger:/var/opt/drd>

/etc/lvmtab does not have any references to drd and looks good and I did move /etc/lvmtab and vgscan -av as part of my troubleshooting. I also only have a drd.conf.old file in /etc/lvmconf. (from the previous drd install)

I am not sure which minor number drd vgcreate is trying to use. Not sure how to get around this error either.

[Michal Kapalka (mikap)]

hi,

did you try to use overwrite option ???

/opt/drd/bin/drd clone -v -x overwrite=true -t (final_disk )


mikap

[S. Ney]

Yes,
I've used -x overwrite=true each time. Doesn't matter which disk I make the target the error is the same.
root@avenger:/root> drd clone -v -x overwrite=true -t /dev/dsk/c0t1d0 -x mirror_disk=/dev/dsk/c1t3d0

======= 09/28/09 08:59:52 EDT BEGIN Clone System Image (user=root) (jobid=avenger)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
* The disk "/dev/dsk/c0t1d0" contains data which will be overwritten.
* The disk "/dev/dsk/c1t3d0" contains data which will be overwritten.
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning
* Creating New File Systems
ERROR: Clone file system creation fails.
- Creating the target file systems fails.
- Command "/opt/drd/lbin/drdconfigure" fails with the return code 255. The errors written by the command are displayed below:
- Start of errors written by /opt/drd/lbin/drdconfigure:
- * Using LVM for disk 0/4/1/0.0.0.1.0 (c0t1d0s2), group: drd00
* Creating LVM physical volume "/dev/rdsk/c0t1d0s2" (0/4/1/0.0.0.1.0).
* Creating volume group "drd00".
ERROR: Command "/sbin/vgcreate -A n -e 4356 -l 255 -p 16 -s 32 /dev/drd00 /dev/dsk/c0t1d0s2" failed.

- End of errors written by /opt/drd/lbin/drdconfigure
- Command "/opt/drd/lbin/drdconfigure" fails with the return code 255. The entire output from the command is given below:
- Start of output from /opt/drd/lbin/drdconfigure:
- Physical volume "/dev/rdsk/c0t1d0s2" has been successfully created.
vgcreate: Volume group "/dev/drd00" could not be created:
A volume group is already using this major and minor number.
Please check the minor number of the "group" device file.

- End of output from /opt/drd/lbin/drdconfigure
* Creating New File Systems failed with 1 error.
* Unmounting New System Image Clone
* System image: "sysimage_001" on disk "/dev/dsk/c0t1d0"
* Cleaning up after clone errors.

[Judy Wathen · Accepted solution]

Hello S. Nev â

I think what you are seeing is a mismatch between the minor numbers the kernel thinks are in use and the ones visible in the device files. DRD will attempt to use the next free group minor number based on the device files, in this case 2, and it looks like the kernel thinks 2 is already in use. You should be able to bypass the probably by creating a group device file using minor number 2:

mkdir /dev/fake
mknod /dev/fake/group c 64 0x020000

Then re-try the drd clone command.
It is not clear what the root cause of the problem is. DRD does attempt to unmount partially mounted clones during an rc script.

(The problem would also go away with a reboot, but I don't image you want to incur the downtime of rebooting the system.)

If this does not bypass the problem, or if you see it repeatedly, please let me know.

Thanks,
Judy

[S. Ney]

Judy,

Thank you. I did reboot the system and that resolved the issue but I've made notes about creating a /dev/fake dir in case I stumble upon this problem again.