General
cancel
Showing results for 
Search instead for 
Did you mean: 

CRS is unable to identify the links created

Amit K
Occasional Advisor

CRS is unable to identify the links created

Hi All,

on of the server on which we are facing issues with Clusterware start up.

On investigation we have found that the Major Number of the disk differ on both the nodes and hence the CRS is unable to identify the links created (usning mknod) to the disks.

PFB the log:
Host 1
$ cd /dev/rdisk/
$ ls -l
total 0
crw-r----- 1 bin sys 22 0x000001 Jan 31 2008 disk46
crw-r----- 1 bin sys 22 0x000002 Jan 31 2008 disk47
crw-r----- 1 bin sys 22 0x000003 Jan 31 2008 disk48

host 2:
# cd /dev/rdisk/
# ls -l
total 0
crw-r----- 1 bin sys 21 0x000001 Jun 1 11:20 disk46
crw-r----- 1 bin sys 21 0x000002 Jun 1 11:20 disk47
crw-r----- 1 bin sys 21 0x000003 Jun 1 11:20 disk48

i had also checked ioscan output
On host 1 below are the disks under disk46

# ioscan -m dsf disk46
Persistent DSF Legacy DSF(s)
========================================
disk46 /dev/rdsk/c1t0d0
/dev/rdsk/c2t0d0
/dev/rdsk/c6t0d0
/dev/rdsk/c9t0d0

But on host2 where issue lies; first disk is diffrent from host 1 output.

ioscan -m dsf disk46
Persistent DSF Legacy DSF(s)
========================================
disk46 /dev/rdsk/c3t0d0
/dev/rdsk/c2t0d0
/dev/rdsk/c6t0d0
/dev/rdsk/c9t0d0

is anything related to this for Major number change?

can anybody help me on this?

Thanks

Amit K
4 REPLIES
Matti_Kurkela
Honored Contributor

Re: CRS is unable to identify the links created

The Major Number of the /dev/rdisk devices should be whatever the "lsdev -d esdisk" command indicates in the "Character" column.

The number may be different on hosts with a different patch level and/or kernel configuration: on my 11.31 system, the character device number was 23.

Using mknod to create disk devices in 11.31 is probably unwise, because the new storage implementation of 11.31 can create new disk devices automatically. The manually-created disk nodes may conflict with the auto-created ones.

If you must create disk devices manually, use mksf/rmsf commands instead of mknod. They can stop you from shooting yourself in the foot: mknod cannot do that.

If your disk device files have been messed up, use "insf -e -Cdisk" to re-create the disk device files to match the kernel's hardware information.

If the CRS requires the major numbers to be the same, it makes an assumption that is no longer true in 11.31.

MK
MK
Amit K
Occasional Advisor

Re: CRS is unable to identify the links created

Thanks MK for your valuable inputs.

I would like to know whether can we recreate device files using insf -e -Cdisk with Major number as 22 without damaging the data on the disks?

We are not in position to take the risk for data corruption.

Can you please suggest on this?

Aneesh Mohan
Honored Contributor

Re: CRS is unable to identify the links created

Hi Amit ,

>>the CRS is unable to identify the links created (usning mknod) to the disks.

Check the permissions ,I belive oracle(CRS) user should have access permission to the voting disk (cat /var/opt/oracle/ocr.loc).

Regards,
Aneesh
skt_skt
Honored Contributor

Re: CRS is unable to identify the links created

here is an example from a LVM and ASM disk. Note the Major number diff. if the ASM file is a link/mknod( I my case it is) the fle can be recreated by rmsf&mknod again.

brw-r----- 1 bin sys 31 0x006000 Apr 12 2007 /dev/dsk/c0t6d0


crw-r--r-- 1 oracle dba 188 0x1a8500 Oct 25 06:30 /dev/rdsk/p594_ASM_data_56

#ll|grep 0x1a8500
crw-r----- 1 bin sys 188 0x1a8500 Oct 8 2008 c26t8d5
crw-r--r-- 1 oracle dba 188 0x1a8500 Oct 25 06:33 p594_ASM_data_56