Major and Minor Number Inconsistency after oracleasm creatdisk for PowerPath (Doc ID 420841.1)

Last updated on JANUARY 19, 2011

Applies to:

Linux OS - Version: 1.0.4 and later   [Release: and later ]
Linux OS - Version: 2.4 to 2.4]
Linux x86
Linux x86-64
***Checked for relevance on 19-Jan-2011***

Symptoms

You create new asm disks using "oracleasm createdisk" but the major/minor numbers used for asm disks are inconsistent across the cluster nodes. For example on node 1:
# ls -l /dev/oracleasm/disks/*
brw-rw---- 1 oracle dba 232, 209 Mar 24 21:45 DISK01
brw-rw---- 1 oracle dba 233, 1 Mar 24 13:15 DISK02
...
and on node 2:
# ls -l /dev/oracleasm/disks/*
brw-rw---- 1 oracle dba 68, 81 Mar 24 13:18 DISK01
brw-rw---- 1 oracle dba 68, 33 Mar 24 13:18 DISK02
...

Changes

New oracleasm disks are defined using:
       # /etc/init.d/oracleasm createdisk DISK01 /dev/emcpowern1
or similar.

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