UDEV SCSI Rules Configuration In Oracle Linux 5, 6 and 7 For Oracle Automatic Storage Man
2018-03-01 12:54
477 查看
Redhat 6环境下Udev相比之前发生了一些变化，因此转载一片文档用以记录
先在节点A对共享存储的磁盘进行分区
fdisk /dev/sdb
n / p / w
new, primary partition, save
之后在另一个节点B刷新并查询分区的信息
partprobe -s
fdisk /dev/sdb
UDEV SCSI Rules Configuration In OracleLinux 5, 6 and 7
For Oracle Automatic Storage Manager (ASM)to use disks, it needs to be able to identify the devices consistently and forthem to have the correct ownership and permissions. In Linux you can use ASMLibto manage these tasks, but it is seen as an additional layer of complexity andhas never really gained any popularity. Instead, many people use the Linuxdevice manager "udev" to perform these tasks. This article presents abrief overview of setting up udev rules with respect to disks for use with ASMin Oracle 11g. The examples are all done using Oracle Linux 5, 6 and 7, so theywill be consistent with RHEL and CentOS 5, 6 and 7.
Background
Identify the Disks (/sbin/scsi_id)
Make SCSI Devices Trusted
Create UDEV Rules File
Load Updated Block Device Partitions (/sbin/partprobe)
Test Rules (udevtest)
Restart UDEV Service
Check Ownership and Permissions
Background
Essentially, what udev does is apply rulesdefined in files in the "/etc/udev/rules.d" directory to the devicenodes listed in the "/dev" directory. The rules can be defined in avariety of ways, but what we need to do is identify the device and say what wewant udev to do with it.
In this case I know all my disk devices arenamed "/dev/sd?1", where the "?" represents a letter froma-d, so I can identify the devices of interest using the following ruleparameters.
KERNEL=="sd?1",BUS=="scsi"
I want to tie each specific device to analias, so it is always identified the same way, regardless of the device nameLinux assigns it. So I need to be able to test each device that matches theprevious pattern to see if it is the disk I am interested in. Each disk has aunique SCSI ID, so I can place a test into the rule, telling it how to performthe test, and the result it should return for a positive match. The followingrule parameters explain how to test the device and what result constitutes a matchin Oracle Linux 5.
PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_"
The scsi_id command works a littledifferently in Oracle Linux 6, so for that the following test works better.
PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_"
The scsi_id command is located in adifferent place in Oracle Linux 7, so for that the following test is correct.
PROGRAM=="/usr/lib/udev/scsi_id -g -u-d /dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_"
Once we have identified the specific deviceof interest, we need to indicate what actions should be performed on it. Thefollowing parameters specify an alias, the ownership and the permissions forthe device.
NAME="asm-disk1",OWNER="oracle", GROUP="dba", MODE="0660"
So the whole rule for each disk will looksomething like this in Oracle Linux 5.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
Or this in Oracle Linux 6.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
Or this in Oracle Linux 7.
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",SYMLINK+="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
This means that the device pointing to thepartition "sd*1" on the disk with the SCSI ID of"SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_" will always be called"/dev/asm-disk1", regardless of the letter "?" Linux assignswhen the device is discovered. In addition, the device will have the correctownership and permissions for ASM.
There are a number of wildcards andmatching patterns that can be used if you don't want to write device-specificrules.
Now we know roughly what we are trying toachieve, we will look at each step necessary for setting up the disks for ASMto use.
Identify the Disks (/sbin/scsi_id)
We are going to write device-specificrules, so we need to be able to identify each device consistently, irrespectiveof the order in which Linux discovers it. To do this we are going to use theSCSI ID for each disk (not the partition), which we get using the scsi_idcommand. The "-s" option makes the paths relative to the"/sys" directory. For Oracle Linux 5, use the following command.
# /sbin/scsi_id -g -u -s /block/sdb
SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_
# /sbin/scsi_id -g -u -s /block/sdc
SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_
# /sbin/scsi_id -g -u -s /block/sdd
SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_
# /sbin/scsi_id -g -u -s /block/sde
SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_
#
The "-s" is not available inOracle Linux 6, so you must use the following syntax.
# /sbin/scsi_id -g -u -d /dev/sdb
SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_
# /sbin/scsi_id -g -u -d /dev/sdc
SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_
# /sbin/scsi_id -g -u -d /dev/sdd
SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_
# /sbin/scsi_id -g -u -d /dev/sde
SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_
#
The location of the scsi_id command haschanged in Oracle Linux 7, so you must use the following syntax.
# /usr/lib/udev/scsi_id -g -u -d /dev/sdb
SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_
# /usr/lib/udev/scsi_id -g -u -d /dev/sdc
SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_
# /usr/lib/udev/scsi_id -g -u -d /dev/sdd
SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_
# /usr/lib/udev/scsi_id -g -u -d /dev/sde
SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_
#
Make SCSI Devices Trusted
Add the following to the"/etc/scsi_id.config" file to configure SCSI devices as trusted.Create the file if it doesn't already exist.
options=-g
Create UDEV Rules File
Create the"/etc/udev/rules.d/99-oracle-asmdevices.rules" file.
# vi/etc/udev/rules.d/99-oracle-asmdevices.rules
The file should contain the following linesfor Oracle Linux 5. The PROGRAM parameter must match the command you used toretrieve the SCSI ID, and the RESULT parameter must match the value returnedfrom your disks.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent",RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_",NAME="asm-disk2", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent",RESULT=="SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_",NAME="asm-disk3", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s /block/$parent",RESULT=="SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_",NAME="asm-disk4", OWNER="oracle", GROUP="dba",MODE="0660"
The equivalent for Oracle Linux 6 is shownbelow.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GR
4000
OUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_",NAME="asm-disk2", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_",NAME="asm-disk3", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_",NAME="asm-disk4", OWNER="oracle", GROUP="dba",MODE="0660"
The equivalent for Oracle Linux 7 is shownbelow.
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",SYMLINK+="asm-disk1", OWNER="oracle",GROUP="dba", MODE="0660"
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_",SYMLINK+="asm-disk2", OWNER="oracle",GROUP="dba", MODE="0660"
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172",SYMLINK+="asm-disk3", OWNER="oracle",GROUP="dba", MODE="0660"
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_",SYMLINK+="asm-disk4", OWNER="oracle", GROUP="dba",MODE="0660"
Load Updated Block Device Partitions(/sbin/partprobe)
Load updated block device partition tables.
# /sbin/partprobe /dev/sdb1
# /sbin/partprobe /dev/sdc1
# /sbin/partprobe /dev/sdd1
# /sbin/partprobe /dev/sde1
Test Rules (udevtest)
Test the rules are working as expected.
# #OL5
# udevtest /block/sdb/sdb1
# udevtest /block/sdc/sdc1
# udevtest /block/sdd/sdd1
# udevtest /block/sde/sde1
# #OL6 and OL7
# udevadm test /block/sdb/sdb1
# udevadm test /block/sdc/sdc1
# udevadm test /block/sdd/sdd1
# udevadm test /block/sde/sde1
The output from the first disk should looksomething like this.
# udevtest /block/sdb/sdb1
main: looking at device '/block/sdb/sdb1'from subsystem 'block'
udev_rules_get_name: add symlink'disk/by-id/scsi-SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3-part1'
udev_rules_get_name: add symlink'disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1'
run_program: '/lib/udev/vol_id --export/dev/.tmp-8-17'
run_program: '/lib/udev/vol_id' returnedwith status 4
run_program: '/sbin/scsi_id -g -u -s/block/sdb/sdb1'
run_program: '/sbin/scsi_id' (stdout)'SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_'
run_program: '/sbin/scsi_id' returned withstatus 0
udev_rules_get_name: rule applied, 'sdb1'becomes 'asm-disk1'
udev_device_event: device '/block/sdb/sdb1'already in database, validate currently present symlinks
udev_node_add: creating device node'/dev/asm-disk1', major = '8', minor = '17', mode = '0660', uid = '1100', gid ='1200'
udev_node_add: creating symlink'/dev/disk/by-id/scsi-SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3-part1' to'../../asm-disk1'
udev_node_add: creating symlink'/dev/disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1' to '../../asm-disk1'
main: run:'socket:/org/kernel/dm/multipath_event'
main: run:'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run:'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply/dev/asm-disk1/dev/disk/by-id/scsi-SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3-part1/dev/disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1'
#
Restart UDEV Service
Restart the UDEV service.
# #OL5
# /sbin/udevcontrol reload_rules
# #OL6 and OL7
# udevadm control --reload-rules
# #OL5 and OL6 : Not needed for OL7
# /sbin/start_udev
Check Ownership and Permissions
Check the disks are now available with the"asm-disk*" alias and the correct ownership and permissions.
# cd /dev
# ls -al asm-disk*
brw-rw---- 1 oracle dba 8, 17 Apr 8 22:47 asm-disk1
brw-rw---- 1 oracle dba 8, 33 Apr 8 22:47 asm-disk2
brw-rw---- 1 oracle dba 8, 49 Apr 8 22:47 asm-disk3
brw-rw---- 1 oracle dba 8, 65 Apr 8 22:47 asm-disk4
#
So the ASM_DISKSTRING initializationparameter in the ASM instance can be set to '/dev/asm-disk*' to identify theASM disks.
For more information see:
udev
Configuring Disk Devices Manually for Oracle ASM
Hope this helps. Regards Tim...
Back to the Top.
先在节点A对共享存储的磁盘进行分区
fdisk /dev/sdb
n / p / w
new, primary partition, save
之后在另一个节点B刷新并查询分区的信息
partprobe -s
fdisk /dev/sdb
UDEV SCSI Rules Configuration In OracleLinux 5, 6 and 7
For Oracle Automatic Storage Manager (ASM)to use disks, it needs to be able to identify the devices consistently and forthem to have the correct ownership and permissions. In Linux you can use ASMLibto manage these tasks, but it is seen as an additional layer of complexity andhas never really gained any popularity. Instead, many people use the Linuxdevice manager "udev" to perform these tasks. This article presents abrief overview of setting up udev rules with respect to disks for use with ASMin Oracle 11g. The examples are all done using Oracle Linux 5, 6 and 7, so theywill be consistent with RHEL and CentOS 5, 6 and 7.
Background
Identify the Disks (/sbin/scsi_id)
Make SCSI Devices Trusted
Create UDEV Rules File
Load Updated Block Device Partitions (/sbin/partprobe)
Test Rules (udevtest)
Restart UDEV Service
Check Ownership and Permissions
Background
Essentially, what udev does is apply rulesdefined in files in the "/etc/udev/rules.d" directory to the devicenodes listed in the "/dev" directory. The rules can be defined in avariety of ways, but what we need to do is identify the device and say what wewant udev to do with it.
In this case I know all my disk devices arenamed "/dev/sd?1", where the "?" represents a letter froma-d, so I can identify the devices of interest using the following ruleparameters.
KERNEL=="sd?1",BUS=="scsi"
I want to tie each specific device to analias, so it is always identified the same way, regardless of the device nameLinux assigns it. So I need to be able to test each device that matches theprevious pattern to see if it is the disk I am interested in. Each disk has aunique SCSI ID, so I can place a test into the rule, telling it how to performthe test, and the result it should return for a positive match. The followingrule parameters explain how to test the device and what result constitutes a matchin Oracle Linux 5.
PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_"
The scsi_id command works a littledifferently in Oracle Linux 6, so for that the following test works better.
PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_"
The scsi_id command is located in adifferent place in Oracle Linux 7, so for that the following test is correct.
PROGRAM=="/usr/lib/udev/scsi_id -g -u-d /dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_"
Once we have identified the specific deviceof interest, we need to indicate what actions should be performed on it. Thefollowing parameters specify an alias, the ownership and the permissions forthe device.
NAME="asm-disk1",OWNER="oracle", GROUP="dba", MODE="0660"
So the whole rule for each disk will looksomething like this in Oracle Linux 5.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
Or this in Oracle Linux 6.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
Or this in Oracle Linux 7.
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",SYMLINK+="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
This means that the device pointing to thepartition "sd*1" on the disk with the SCSI ID of"SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_" will always be called"/dev/asm-disk1", regardless of the letter "?" Linux assignswhen the device is discovered. In addition, the device will have the correctownership and permissions for ASM.
There are a number of wildcards andmatching patterns that can be used if you don't want to write device-specificrules.
Now we know roughly what we are trying toachieve, we will look at each step necessary for setting up the disks for ASMto use.
Identify the Disks (/sbin/scsi_id)
We are going to write device-specificrules, so we need to be able to identify each device consistently, irrespectiveof the order in which Linux discovers it. To do this we are going to use theSCSI ID for each disk (not the partition), which we get using the scsi_idcommand. The "-s" option makes the paths relative to the"/sys" directory. For Oracle Linux 5, use the following command.
# /sbin/scsi_id -g -u -s /block/sdb
SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_
# /sbin/scsi_id -g -u -s /block/sdc
SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_
# /sbin/scsi_id -g -u -s /block/sdd
SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_
# /sbin/scsi_id -g -u -s /block/sde
SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_
#
The "-s" is not available inOracle Linux 6, so you must use the following syntax.
# /sbin/scsi_id -g -u -d /dev/sdb
SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_
# /sbin/scsi_id -g -u -d /dev/sdc
SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_
# /sbin/scsi_id -g -u -d /dev/sdd
SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_
# /sbin/scsi_id -g -u -d /dev/sde
SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_
#
The location of the scsi_id command haschanged in Oracle Linux 7, so you must use the following syntax.
# /usr/lib/udev/scsi_id -g -u -d /dev/sdb
SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_
# /usr/lib/udev/scsi_id -g -u -d /dev/sdc
SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_
# /usr/lib/udev/scsi_id -g -u -d /dev/sdd
SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_
# /usr/lib/udev/scsi_id -g -u -d /dev/sde
SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_
#
Make SCSI Devices Trusted
Add the following to the"/etc/scsi_id.config" file to configure SCSI devices as trusted.Create the file if it doesn't already exist.
options=-g
Create UDEV Rules File
Create the"/etc/udev/rules.d/99-oracle-asmdevices.rules" file.
# vi/etc/udev/rules.d/99-oracle-asmdevices.rules
The file should contain the following linesfor Oracle Linux 5. The PROGRAM parameter must match the command you used toretrieve the SCSI ID, and the RESULT parameter must match the value returnedfrom your disks.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent",RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_",NAME="asm-disk2", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s/block/$parent",RESULT=="SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_",NAME="asm-disk3", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s /block/$parent",RESULT=="SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_",NAME="asm-disk4", OWNER="oracle", GROUP="dba",MODE="0660"
The equivalent for Oracle Linux 6 is shownbelow.
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",NAME="asm-disk1", OWNER="oracle", GR
4000
OUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_",NAME="asm-disk2", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172_",NAME="asm-disk3", OWNER="oracle", GROUP="dba",MODE="0660"
KERNEL=="sd?1",BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_",NAME="asm-disk4", OWNER="oracle", GROUP="dba",MODE="0660"
The equivalent for Oracle Linux 7 is shownbelow.
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_",SYMLINK+="asm-disk1", OWNER="oracle",GROUP="dba", MODE="0660"
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_",SYMLINK+="asm-disk2", OWNER="oracle",GROUP="dba", MODE="0660"
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBce8c63bb-ac67a172",SYMLINK+="asm-disk3", OWNER="oracle",GROUP="dba", MODE="0660"
KERNEL=="sd?1",SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d/dev/$parent",RESULT=="SATA_VBOX_HARDDISK_VB7437a3b7-95b199cd_",SYMLINK+="asm-disk4", OWNER="oracle", GROUP="dba",MODE="0660"
Load Updated Block Device Partitions(/sbin/partprobe)
Load updated block device partition tables.
# /sbin/partprobe /dev/sdb1
# /sbin/partprobe /dev/sdc1
# /sbin/partprobe /dev/sdd1
# /sbin/partprobe /dev/sde1
Test Rules (udevtest)
Test the rules are working as expected.
# #OL5
# udevtest /block/sdb/sdb1
# udevtest /block/sdc/sdc1
# udevtest /block/sdd/sdd1
# udevtest /block/sde/sde1
# #OL6 and OL7
# udevadm test /block/sdb/sdb1
# udevadm test /block/sdc/sdc1
# udevadm test /block/sdd/sdd1
# udevadm test /block/sde/sde1
The output from the first disk should looksomething like this.
# udevtest /block/sdb/sdb1
main: looking at device '/block/sdb/sdb1'from subsystem 'block'
udev_rules_get_name: add symlink'disk/by-id/scsi-SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3-part1'
udev_rules_get_name: add symlink'disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1'
run_program: '/lib/udev/vol_id --export/dev/.tmp-8-17'
run_program: '/lib/udev/vol_id' returnedwith status 4
run_program: '/sbin/scsi_id -g -u -s/block/sdb/sdb1'
run_program: '/sbin/scsi_id' (stdout)'SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_'
run_program: '/sbin/scsi_id' returned withstatus 0
udev_rules_get_name: rule applied, 'sdb1'becomes 'asm-disk1'
udev_device_event: device '/block/sdb/sdb1'already in database, validate currently present symlinks
udev_node_add: creating device node'/dev/asm-disk1', major = '8', minor = '17', mode = '0660', uid = '1100', gid ='1200'
udev_node_add: creating symlink'/dev/disk/by-id/scsi-SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3-part1' to'../../asm-disk1'
udev_node_add: creating symlink'/dev/disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1' to '../../asm-disk1'
main: run:'socket:/org/kernel/dm/multipath_event'
main: run:'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run:'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply/dev/asm-disk1/dev/disk/by-id/scsi-SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3-part1/dev/disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1'
#
Restart UDEV Service
Restart the UDEV service.
# #OL5
# /sbin/udevcontrol reload_rules
# #OL6 and OL7
# udevadm control --reload-rules
# #OL5 and OL6 : Not needed for OL7
# /sbin/start_udev
Check Ownership and Permissions
Check the disks are now available with the"asm-disk*" alias and the correct ownership and permissions.
# cd /dev
# ls -al asm-disk*
brw-rw---- 1 oracle dba 8, 17 Apr 8 22:47 asm-disk1
brw-rw---- 1 oracle dba 8, 33 Apr 8 22:47 asm-disk2
brw-rw---- 1 oracle dba 8, 49 Apr 8 22:47 asm-disk3
brw-rw---- 1 oracle dba 8, 65 Apr 8 22:47 asm-disk4
#
So the ASM_DISKSTRING initializationparameter in the ASM instance can be set to '/dev/asm-disk*' to identify theASM disks.
For more information see:
udev
Configuring Disk Devices Manually for Oracle ASM
Hope this helps. Regards Tim...
Back to the Top.
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5, 6 and 7
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5, 6 and 7
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5, 6 and 7
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
- UDEV SCSI Rules Configuration In Oracle Linux 5, 6 and 7
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5 and 6
- UDEV SCSI Rules Configuration for ASM in Oracle Linux 5, 6 and 7
- Redmine Installation and Configuration in Linux
- Java Development Environment in Linux: Install and Configure Oracle
- How to use udev for Oracle ASM in Oracle Linux 6 怎样使用udev在linux 6系统上使用asm
- How to use udev for Oracle ASM in Oracle Linux 5
- skpye 4.3 installation and configuration in linux CentOS 7 / RHEL 7 / Fedora 20
- 如何用udev for asm in oracle linux 6
- How to use udev for Oracle ASM in Oracle Linux 6
- (转)How to use udev for Oracle ASM in Oracle Linux 6