DRD fail with a hang-up signal

[NDO]

Hi All

Please can you assist on this : I have a system running 11.23, I have install DRD, and I had a disk that I did not initialize (LVM) the disk (c40t0d0).

I run the following:

drd clone -v -x overwrite=true -t /dev/dsk/c40t0d0

=======  09/28/11 17:12:57 SASTT  BEGIN  Clone System Image (user=root)
         (jobid=mceldev)

       * Reading Current System Information
       * Selecting System Image To Clone
       * Selecting Target Disk
       * The disk "/dev/dsk/c40t0d0" contains data which will be overwritten.
       * Selecting Volume Manager For New System Image
       * Analyzing For System Image Cloning
       * Creating New File Systems
       * Copying File Systems To New System Image
ERROR:   Exiting due to hang-up signal.
       * Unmounting New System Image Clone
       * System image: "sysimage_001" on disk "/dev/dsk/c40t0d0"
       * Cleaning up after clone errors.
       * Copying File Systems To New System Image failed with 1 error.

=======  09/28/11 19:27:16 SASTT  END  Clone System Image failed with 1 error.
         (user=root)  (jobid=mceldev)

Any ideas that what could have gone wrong? Do you have to initialize the disk? by pvcreate?

FR

[Hiren N Dave]

pvcreate is not required.

Try to pvremove on the device and run drdclone again.

[NDO]

Hi

From the man pages, pvremove will remove any LVM structures on the disk, but that disk was never initialized LVM wise.

Can I run drd while a database is up? Although I did run drd clone when nothing was up.

[Hiren N Dave]

> * Creating New File Systems

PV might have LVM structure on it due to above message from drd clone output..

Try to run

# pvdisplay -l /dev/dsk/c40t0d0

to find out if this disk has LVM structure created on it and try pvremove to remove LVM structure from it. Although -x overwrite=true does not require this step.

Refer to this link:->  http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01918754/c01918754.pdf

The target disk must:

• Be a block device special file.

• Be writeable by the system.

• Not currently be in use by other applications.

• Be large enough to hold a copy of each logical volume in the root group.

[NDO]

Hi

I did:

pvdisplay -l /dev/dsk/c40t0d0
/dev/dsk/c40t0d0:LVM_Disk=no

So its not a LVM disk, and from ioscan -fnC disk, I got:

disk      1  0/1/1/0.0.0    sdisk      CLAIMED     DEVICE       HP 146 GST3146707LC
                           /dev/dsk/c2t0d0   /dev/rdsk/c2t0d0
disk      2  0/1/1/0.1.0    sdisk      CLAIMED     DEVICE       HP 146 GST3146707LC
                           /dev/dsk/c2t1d0     /dev/dsk/c2t1d0s2   /dev/rdsk/c2t1d0    /dev/rdsk/c2t1d0s2
                           /dev/dsk/c2t1d0s1   /dev/dsk/c2t1d0s3   /dev/rdsk/c2t1d0s1  /dev/rdsk/c2t1d0s3

and there is another disk that is part of vg00 which is 120Gb, so in total is 412Gb. But less than 220Gb are being used by vg00, and the target disk c40t0d0 (clone disk) is only 250Gb.

Shall I have to have a target clone disk with same size of the disks in vg00 which are 412Gb?

[Hiren N Dave]

The target's physical disk need not be as large as the disk allocated for the root group, as long
as there is enough space for a copy of each logical volume in the root group. However, the disk
needs to be larger than the used space in each logical volume because each logical volume will
be created with the number of physical extents currently allocated to the corresponding root
group logical volume.

You can use drd clone with the -p option to get minimal availability information about a disk.

# /opt/drd/bin/drd clone –p –v –t /dev/dsk/cxtxdx

The preview operation includes disk space analysis that shows whether a target disk is large
enough. If you prefer to investigate disk sizes before previewing the clone, you can use the
diskinfo command.

[NDO]

Hi

From running "vgdisplay -v /dev/vg00 | more" I can see that PE size is 32 and Alloc PE is 7521, so roughly 240Gb of space is being used, and my target disk is exactly 250Gb. I beleive this should not be a problem.

#vgdisplay -v /dev/vg00 | more
--- Volume groups ---
VG Name                     /dev/vg00
VG Write Access             read/write
VG Status                   available
Max LV                      255
Cur LV                      13
Open LV                     13
Max PV                      16
Cur PV                      2
Act PV                      2
Max PE per PV               4356
VGDA                        4
PE Size (Mbytes)            32
Total PE                    8185
Alloc PE                    7521
Free PE                     664
Total PVG                   0

AND

using the preview mode:

#drd clone -p -v -t /dev/dsk/c40t0d0

=======  09/29/11 11:34:44 SASTT  BEGIN  Clone System Image Preview (user=root)  (jobid=mceldev)

       * Reading Current System Information
       * Selecting System Image To Clone
       * Selecting Target Disk
NOTE:    There may be LVM 2 volumes configured that will not be recognized.
ERROR:   Selection of the target disk fails.
         - Selecting the target disk fails.
         - Validation of the disk "/dev/dsk/c40t0d0" fails with the following error(s):
         - The disk "/dev/dsk/c40t0d0" contains data. To overwrite this disk use the option "-x overwrite=true".
       * Selecting Target Disk failed with 1 error.
       * DRD operation failed, contents of /var/opt/drd/tmp copied to /var/opt/drd/save.

=======  09/29/11 11:35:02 SASTT  END  Clone System Image Preview failed with 1 error. (user=root)  (jobid=mceldev)

[Pete Randall]

> To overwrite this disk use the option "-x overwrite=true".

[NDO]

Hi

I did use that command initially: drd clone -v -x overwrite=true -t /dev/dsk/c40t0d0, but it come up with that hang-up signal failure

[Pete Randall]

Sorry, I didn't read your initial post carefully enough.  Seems to be sort of Catch22!

[NDO]

Any ideas how to solve this?

[Pete Randall]

/dev/dsk/c40t0d0 seems like a kind of an unusual device (c40?).  What does "diskinfo /dev/rdsk/c40t0d0" return?

[NDO]

its

#diskinfo /dev/rdsk/c40t0d0
SCSI describe of /dev/rdsk/c40t0d0:
             vendor: NETAPP
         product id: LUN
               type: direct access
               size: 262144000 Kbytes
   bytes per sector: 512

[Patrick Wallek]

A "hang-up" indicates to me that something, or someone, did a 'kill -1' on the DRD process.

I just duplicated your error by doing just that.

[Pete Randall]

It seems you're running this through some sort of job scheduler perhaps????  Have you tried just doing it from the command line?

Thanks, Patrick!

[NDO]

Hi

I did run it from the command line, for sure

Patrick!

I am using ssh putty session that if stays idle for more than 10 minutes losses the connection to the server. Would this be the culprit, causing a kill -1?

[Pete Randall]

> if stays idle for more than 10 minutes . . . .Would this be the culprit

You tell us.  Did it take 10 minutes to fail?  How is "idle" defined?  Screen I/O activity?

[James R. Ferguson · Accepted solution]

---

@Nandinho wrote:

I am using ssh putty session that if stays idle for more than 10 minutes losses the connection to the server. Would this be the culprit, causing a kill -1?

---

As the parent process the PuTTY session,  a SIGHUP would be sent to the DRD process, killing it.  You could avoid this by starting it with 'nohup' in the background.  You could defeat whatever timeout the session enforces too.

Regards!

...JRF...

[NDO]

sorry I should have look it, I can see on /var/opt/drd/drd.log, that yesterday session started at 17:12:57 and ended with error at 19:27:16.

[NDO]

Thanks JRF,

I will try that in couple hours when the database can be shutdown.

FR

[NDO]

JRF

nohup did the trick, I ´ve checked the drd.log and run drd status and I got this:

drd status

=======  09/30/11 08:06:06 SASTT  BEGIN  Displaying DRD Clone Image Information (user=root)  (jobid=mceldev)

       * Clone Disk:               /dev/dsk/c40t0d0
       * Clone EFI Partition:      AUTO file present, Boot loader present
       * Clone Rehost Status:      SYSINFO.TXT not present
       * Clone Creation Date:      09/29/11 17:06:43 SAST
       * Last Sync Date:           None
       * Clone Mirror Disk:        None
       * Mirror EFI Partition:     None
       * Original Disk:            /dev/dsk/c2t1d0
       * Original EFI Partition:   AUTO file present, Boot loader present
       * Original Rehost Status:   SYSINFO.TXT not present
       * Booted Disk:              Original Disk (/dev/dsk/c2t1d0)
       * Activated Disk:           Original Disk (/dev/dsk/c2t1d0)

=======  09/30/11 08:06:22 SASTT  END  Displaying DRD Clone Image Information succeeded. (user=root)  (jobid=mceldev)

Thanks

FR