This discussion is archived
1 Reply Latest reply: Feb 26, 2013 9:08 AM by damorgan RSS

ASM_DISKSTRING is empty and discover discs

AminChavarria Newbie
Currently Being Moderated
Hi,

SO: RHEL6
GI: 11.2.0.3
User owner: grid

The parameter ASM_DISKSTRING is null string however discovers disks.

SQL> select name, path from v$asm_disk;

NAME                           PATH
------------------------------ --------------------------------------------------
                               /dev/vg_hdisk_ora/lv_hd10
                               /dev/vg_hdisk_ora/lv_hd15
                               /dev/vg_hdisk_ora/lv_hd3
                               /dev/vg_hdisk_ora/lv_hd6
                               /dev/vg_hdisk_ora/lv_hd4
                               /dev/vg_hdisk_ora/lv_hd7
                               /dev/vg_hdisk_ora/lv_hd5
                               /dev/vg_hdisk_ora/lv_hd2
                               /dev/vg_hdisk_ora/lv_hd8
                               /dev/vg_hdisk_ora/lv_hd9
                               /dev/vg_hdisk_ora/lv_hd20
                               /dev/vg_hdisk_ora/lv_hd18
                               /dev/vg_hdisk_ora/lv_hd17
                               /dev/vg_hdisk_ora/lv_hd19
                               /dev/vg_hdisk_ora/lv_hd16
                               /dev/vg_hdisk_ora/lv_hd14
                               /dev/vg_hdisk_ora/lv_hd11
                               /dev/vg_hdisk_ora/lv_hd13
                               /dev/vg_hdisk_ora/lv_hd12
                               /dev/vg_hdisk_ora/lv_hd1

20 rows selected.

SQL> show parameters string

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskstring                       string
After setting asm_diskstring to "/dev/asm*", list 40 disks (kernel-assigned device file names & UDEV name)
DISK_NUMBER PATH
----------- ----------------------------------------
          0 /dev/asm-disk10
         39 /dev/vg_hdisk_ora/lv_hd15
          2 /dev/asm-disk3
          3 /dev/asm-disk6
          4 /dev/asm-disk4
          5 /dev/asm-disk7
          6 /dev/asm-disk5
          7 /dev/asm-disk2
          8 /dev/asm-disk8
          9 /dev/asm-disk9
         10 /dev/asm-disk20
         11 /dev/asm-disk18
         12 /dev/asm-disk17
         13 /dev/asm-disk19
         14 /dev/asm-disk16
         15 /dev/asm-disk14
         16 /dev/asm-disk11
         17 /dev/asm-disk13
         18 /dev/asm-disk12
         19 /dev/asm-disk15
         20 /dev/vg_hdisk_ora/lv_hd10
         21 /dev/vg_hdisk_ora/lv_hd1
         22 /dev/vg_hdisk_ora/lv_hd3
         23 /dev/vg_hdisk_ora/lv_hd6
         24 /dev/vg_hdisk_ora/lv_hd4
         25 /dev/vg_hdisk_ora/lv_hd7
         26 /dev/vg_hdisk_ora/lv_hd5
         27 /dev/vg_hdisk_ora/lv_hd2
         28 /dev/vg_hdisk_ora/lv_hd8
         29 /dev/vg_hdisk_ora/lv_hd9
         30 /dev/vg_hdisk_ora/lv_hd20
         31 /dev/vg_hdisk_ora/lv_hd18
         32 /dev/vg_hdisk_ora/lv_hd17
         33 /dev/vg_hdisk_ora/lv_hd19
         34 /dev/vg_hdisk_ora/lv_hd16
         35 /dev/vg_hdisk_ora/lv_hd14
         36 /dev/vg_hdisk_ora/lv_hd11
         37 /dev/vg_hdisk_ora/lv_hd13
         38 /dev/vg_hdisk_ora/lv_hd12
          1 /dev/asm-disk1

40 rows selected.
1. Why not list only the names of devices UDEV?

2. Is this normal when creating UDEV rules to ASM?



regards
Amin

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points