cancel
Showing results for 
Search instead for 
Did you mean: 

drd overwrite failure

 

drd overwrite failure

Hi,
When I issue the command:
# drd clone -x overwrite=true -t /dev/disk/disk4
I get the following output after approx 1 minute:
======= 06/11/09 10:51:18 SASTT BEGIN Clone System Image (user=root)

(jobid=unxndp03)



* Reading Current System Information

* Selecting System Image To Clone

* Selecting Target Disk

(0) 0x60000000dbf5cf80 _ZN5OSAPI10stackTraceEv + 0x2e0 at lib/OSAPI_basic.cc:870 [/opt/drd/lib/libcommon.1]

(1) 0x60000000dbfc6de0 _ZN10SMDprivate17FatalEventHandler12handleSignalEi + 0x120 at logmgmt/FatalEventHandler.cc:59 [/opt/drd/lib/libcommon.1]

(2) 0x60000000dbfc6a90 _ZN10SMDprivate13SignalHandler10dispatcherEi + 0x190 at logmgmt/SignalHandler.cc:55 [/opt/drd/lib/libcommon.1]

(3) 0xe00000012068ec80 ---- Signal 11 (SIGSEGV) delivered ----

(4) 0x60000000dbcc3da0 _ZN10SMDprivate12SystemConfig17diskHasPriorUsageERKSs + 0x4e0 at system/SystemConfig.cc:996 [/opt/drd/lib/libsyscore.1]

(5) 0x60000000dbcbf3c0 _ZN10SMDprivate14SystemImageMgr12validateDiskEPNS_12SystemConfigERKSsPN3SMD15DRDRegistryDataE + 0x510 at system/SystemImageMgr.cc:1670 [/opt/drd/lib/libsyscore.1]

(6) 0x60000000dbcbbcd0 _ZN10SMDprivate14SystemImageMgr15initTargetImageEPNS_12SystemConfigESsSsPN3SMD15DRDRegistryDataE + 0x3a0 at system/SystemImageMgr.cc:1670 [/opt/drd/lib/libsyscore.1]

(7) 0x60000000dbcb9590 _ZN10SMDprivate14SystemImageMgr17chooseTargetDisksEPNS_12SystemConfigEPN3SMD15DRDRegistryDataE + 0x1040 at system/SystemImageMgr.cc:1670 [/opt/drd/lib/libsyscore.1]

(8) 0x60000000dbd31940 _ZN10SMDprivate10SysCoreAPI17chooseTargetDisksEPN3SMD15DRDRegistryDataE + 0x260 at ../common/include/Debug.h:317 [/opt/drd/lib/libsyscore.1]

(9) 0x60000000db8c11e0 _ZN10SMDprivate19CloneDRDSysUserTask22doChooseTgtDisksActionEv + 0x220 at /build/sandboxes/080117_2300/src/drd/../common/include/Debug.h:317 [/opt/drd/lib/libdrd.1]

(10) 0x60000000db8b6690 _ZN10SMDprivate19CloneDRDSysUserTask12stateMachineEv + 0x3a10 at usertasks/CloneDRDSysUserTask_stateMachine.cc:434 [/opt/drd/lib/libdrd.1]

(11) 0x60000000dc13fa30 _ZN10SMDprivate8UserTask7runTaskEv + 0x200 at usertasks/UserTask.cc:294 [/opt/drd/lib/libcommon.1]

(12) 0x60000000dc00d740 _ZN10SMDprivate4Task3runEv + 0x2d0 [/opt/drd/lib/libcommon.1]

(13) 0x60000000dc008bc0 _ZN3SMD13SMDJobManager3runESs + 0x4d0 at jobtask/SMDJobManager.cc:145 [/opt/drd/lib/libcommon.1]

(14) 0x60000000dbe344f0 _ZN3SMD3CLI3runEPSt4listIPNS_8TaskDataESaIS3_EE + 0xb90 [/opt/drd/lib/libcommon.1]

(15) 0x000000000400e0d0 _Z7smdmainiPPc + 0x860 at main.cc:252 [/opt/drd/bin/drd]

(16) 0x60000000dc084ef0 _ZN3SMD7SMDinit7smdinitEPFiiPPcEiS2_ + 0x7f0 at main/SMDinit.cc:291 [/opt/drd/lib/libcommon.1]

(17) 0x000000000400d570 main + 0x30 [/opt/drd/bin/drd]

(18) 0x60000000c002a430 main_opd_entry + 0x50 [/usr/lib/hpux32/dld.so]

************
In /var/opt/drd/tmp I am able to see a folder drdtXRPpChb with a bunch of files:

-rw------- 1 root sys 56 Jun 11 10:50 1RnMcFGSd
-rw------- 1 root sys 0 Jun 11 10:51 A0T3hJfWP
-rw------- 1 root sys 0 Jun 11 10:51 Dpwxl90gf
-rw------- 1 root sys 0 Jun 11 10:51 TR11pq4o9
-rw------- 1 root sys 137 Jun 11 10:51 dUoHeTqnB
-rw------- 1 root sys 41 Jun 11 10:51 guu9ZsG9
-rw------- 1 root sys 0 Jun 11 10:51 ofNdotwfi
-rw------- 1 root sys 43 Jun 11 10:51 s4w4IUMg
-rw------- 1 root sys 36100 Jun 11 10:51 sconfG6WAwgSo
-rw------- 1 root sys 137 Jun 11 10:51 vBT05KTAB
-rw------- 1 root sys 137 Jun 11 10:51 vnqtmc5

There are no errors in these files.
The drd.log file doesn't provide any real clue as to why the drd fails:

======= 06/11/09 10:51:18 SASTT BEGIN Clone System Image (user=root)
(jobid=unxndp03)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk

When we ran the drd a few months ago it worked fine. We also have an identical host where drd is working fine.
Any ideas?

Regards
Graham
6 REPLIES
Michal Kapalka (mikap)
Honored Contributor

Re: drd overwrite failure

hi,

check with drd status

Did you activated the clone

mikap

PS: when i tested the drd on our testing system it was the same.

Re: drd overwrite failure

Hi Michal,

Output from drd status:
# drd status

======= 06/11/09 12:27:34 SASTT BEGIN Displaying DRD Clone Image Information
(user=root) (jobid=unxndp03)

* Clone Disk: /dev/disk/disk4
* Clone EFI Partition: Boot loader and AUTO file present
* Clone Creation Date: 11/26/08 14:36:20 SAST
* Clone Mirror Disk: None
* Mirror EFI Partition: None
* Original Disk: /dev/disk/disk5
* Original EFI Partition: Boot loader and AUTO file present
* Booted Disk: Original Disk (/dev/disk/disk5)
* Activated Disk: Original Disk (/dev/disk/disk5)

======= 06/11/09 12:27:43 SASTT END Displaying DRD Clone Image Information
succeeded. (user=root) (jobid=unxndp03)

Regards
Graham
Michal Kapalka (mikap)
Honored Contributor

Re: drd overwrite failure

Hi Graham,

it seems to be everithing ok,

did you activated the inage ???

or mounted ?? If its possible try to reboo the system.

and tme try again to overwrite the disk4 with a new clone.

mikap
Michal Kapalka (mikap)
Honored Contributor

Re: drd overwrite failure

hi,

try to when you are cloning the disk to use -v option it will be more verbose output so you should be able see in wich step it is failing.

mikap

Re: drd overwrite failure

Hi,
I rebooted the system, but this didn't help.
If i issue a "drd runcmd swlist" the command works correctly.

The -v option did not provide any further information.

Regards
Graham
Michal Kapalka (mikap)
Honored Contributor

Re: drd overwrite failure

hi,

the last time that i wasn't able to drd clone the disk, i reignited the server before the DRD depot was installed.

mikap