New 11.2 Grid Infrastructure Installation (root.sh) Is Removing Candidate mknod devices Or Symbolic Link Devices Created At /dev/asm Directory. (Doc ID 1366159.1)

Last updated on APRIL 26, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 18-Jul-2013***

Symptoms


i) Sometimes, in order to define and associated meaningful device names to Candidate or Member physical ASM Disks on Linux/Unix, mknod devices <Document 1313687.1> or symbolic links are used to reference the real raw devices, this practice is completely valid and supported.

ii) But on ASM 11.2 release, there is a specific issue, when you place/create mknod devices or symbolic links at the "/dev/asm" directory, as the following example:



1) The /dev/asm/ASMDISK directory is created on each RAC node.

2) Then several mknod devices were created at the "/dev/asm/ASMDISK" directory referencing the real raw devices (e.g. /dev/rdsk Solaris):



-bash-3.2$ ls -l /dev/asm/ASMDISK/crs
total 0
crw-rw---- 1 oracle dba 118, 4288 Aug 29 15:12 crs_vote_OCR_raw

-bash-3.2$ ls -l /dev/asm/ASMDISK/data
total 0
crwxr-x--- 1 oracle dba 118, 96 Aug 25 16:04 data_raw

-bash-3.2$ ls -l /dev/asm/ASMDISK/archives
total 0
crwxr-x--- 1 oracle dba 118, 104 Aug 25 16:04 arch_raw



3) Then the 11.2 Grid Infrastructure Oracle Home was installed on each RAC node.

4) But after root.sh script is executed on the first node (as root user), all the mknod devices and the subdirectory structure "/dev/asm/ASMDISK" were wiped out (Note: "/dev/asm" directory is removed and recreated during the root.sh execution):


-bash-3.2$ ls -l /dev/asm
total 0

<< no subdirectories or mknod devices>>

 

5) root.sh was trussed using the truss OS command and it clearly shows that the directories are removed and "/dev/asm" directory is recreated during the root.sh execution:


.
.
.
mini_truss.txt:26370: rmdir("archives") = 0
mini_truss.txt:26370: rmdir("crs") = 0
mini_truss.txt:26370: rmdir("data") = 0
mini_truss.txt:26370: rmdir("ASMDISK") = 0
mini_truss.txt:26370: rmdir("/dev/asm") = 0
.
.
.
mini_truss.txt:26296: mkdir("/dev/asm", 0777) = 0
.
.
.

 

6) After the root.sh execution completes, the "/dev/asm" directory is recreated and hidden files (ACFS/ADVM related) were created at the "/dev/asm" directory:


/dev/asm:
total 36
drwxrwx--- 2 root dba 512 Aug 30 14:37 .
drwxr-xr-x 24 root sys 5120 Aug 30 14:37 ..
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_spec ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_spec
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg0 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg0
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg1 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg1
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg2 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg2
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg3 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg3
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg4 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg4
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg5 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg5
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg6 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg6
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg7 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg7
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vbg8 ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vbg8
lrwxrwxrwx 1 root root 47 Aug 30 14:37 .asm_ctl_vdbg ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vdbg
lrwxrwxrwx 1 root root 46 Aug 30 14:37 .asm_ctl_vmb ->
../../devices/pseudo/oracleadvm@0:.asm_ctl_vmb
 



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms