3 Replies Latest reply: Oct 18, 2013 2:35 AM by JohnWatson RSS

    Can ASMLib and udev disks co-exist

    spiral

      Grid version:11.2.0.3

      OS : RHEL 5.8

       

       

      Currently we use ASMLib to stamp our LUNs. We want to start using udev for the device persistancy in our RAC Nodes.

      Can disks labelled using ASMLib and disks named by udev co-exist in a single disk group ?

        • 1. Re: Can ASMLib and udev disks co-exist
          gottikere

          If /ect/init.d/oracleasm listdisk command lists the disk named by udev , than you can put them in single diskgroup.

           

          Thanks,

          http://gssdba.wordpress.com

          • 2. Re: Can ASMLib and udev disks co-exist
            Billy~Verreynne

            What do you mean by "stamp the LUN"?

             

            If it means writing a disk label - ASMLib is not needed for that as ASM itself writes the disk label/header to disk (upon doing commands like create diskgroup).

             

            If it means creating a logical device/symbolic link to a LUN - then no, ASMLib can no longer be used for this as udev/multipath will create the required devices and logical devices.

             

            ASM itself does not care what the o/s calls the device. It does not use that name to identify anything. A disk is always opened and the header read, in order to determine if that disk is an existing or former diskgroup member, or an available disk (one without an ASM disk label).

             

            This means that you should be able to rip out ASMlib, use multipath instead, and simply change the ASM disk discovery string to /dev/mpath, in order for ASM to mount its diskgroups.

            • 3. Re: Can ASMLib and udev disks co-exist
              JohnWatson

              I don't see why you can't mix udev and ASMlib defined devices, just set your asm_diskstring accordingly. In this example, I'm mixing ASMlib and NFS devices and it works no problem:

               

              SQL>

              SQL> sho parameter asm_d

               

              NAME                                 TYPE        VALUE

              ------------------------------------ ----------- ------------------------------

              asm_diskgroups                       string      ACFSV1, ACFSV2

              asm_diskstring                       string      ORCL:*, /u01/nfs_shares/asm/ir

                                                               on*

              SQL> select path from v$asm_disk;

               

              PATH

              --------------------------------------------------------------------------------

              /dev/oracleasm/disks/LUN5

              /dev/oracleasm/disks/LUN4

              /dev/oracleasm/disks/LUN3

              /dev/oracleasm/disks/LUN2

              ORCL:LUN5

              /dev/oracleasm/disks/LUN1

              /u01/nfs_shares/asm/irond5

              ORCL:LUN1

              ORCL:LUN2

              ORCL:LUN3

              ORCL:LUN4

              /u01/nfs_shares/asm/irond3

              /u01/nfs_shares/asm/irond2

              /u01/nfs_shares/asm/irond4

              /u01/nfs_shares/asm/irond1

              /u01/nfs_shares/asm/irond6

               

              16 rows selected.

               

              SQL>