Saw the Liu Xiang soldier Big:
use Udev on Linux 6 to troubleshoot RAC ASM storage device name ProblemsI operated a, previously in the linux5 when I was using asmlib to bind ASM, reference to think twice, I am in the creation of virtual hard disk in the SCSI format of the hard drive, in the Linux 5 when there is no problem, but I am in Linux 6 There is a problem with Udev binding asm: For I in B c D E F; Do echo "kernel==" sd*, bus== "scsi", program== "/sbin/scsi_id--whitelisted--replace-whitespace--device=/dev/$name", result== "'/sbin/scsi_id--whitelisted--replace-whitespace--device=/dev/sd$i '", name= "asm-disk$i", OWNER= "grid", Group= "Asmadmin", mode= "0660" ">>/etc/udev/rules.d/99-oracle-asmdevices.rules Done
The following results occur with SATA disks: cat/etc/udev/rules.d/99-oracle-asmdevices.rules kernel== "sd*", bus== "scsi", program== "/sbin/" scsi_id--whitelisted--replace-whitespace--device=/dev/$name ", result==" 1ata_vbox_harddisk_vb256b1aea-3611084c ", Name= "ASM-DISKB", owner= "grid", group= "Asmadmin", mode= "0660" kernel== "sd*", bus== "scsi", program== "/sbin/scsi_id"- Whitelisted--replace-whitespace--device=/dev/$name ", result==" 1ata_vbox_harddisk_vbca4570d0-4085ffeb ", NAME=" ASM-DISKC ", owner=" grid ", group=" Asmadmin ", mode=" 0660 "kernel==" sd* ", bus==" scsi ", program=="/sbin/scsi_id "- Whitelisted--replace-whitespace--device=/dev/$name ", result==" 1ata_vbox_harddisk_vbb7fbae44-e17451ae ", NAME=" ASM-DISKD ", owner=" grid ", group=" Asmadmin ", mode=" 0660 "kernel==" sd* ", bus==" scsi ", program=="/sbin/scsi_id "- Whitelisted--replace-whitespace--device=/dev/$name ", result==" 1ata_vbox_harddisk_vb759629c7-14b4c298 ", NAME=" Asm-diske ", owner=" grid ", group=" Asmadmin ", mode=" 0660 "kernel==" sd* ", bus==" scsi ", program=="/SB "in/scsi_id--whitelisted--replace-whitespace--device=/dev/$name ", result==" 1ata_vbox_harddisk_ Vbdd7be2b1-4d4a8b29 ", name=" ASM-DISKF ", owner=" grid ", group=" Asmadmin ", mode=" 0660 "
Disk UUID that correctly identifies ASM disk
[Root@node2 dev]# ls-l/dev/asm* brw-rw----. 1 Grid dba 8, Feb 20:57/dev/asm-diskb BRW-RW----. 1 Grid dba 8, Feb 20:57/DEV/ASM-DISKC BRW-RW----. 1 Grid dba 8, Feb 20:57/DEV/ASM-DISKD BRW-RW----. 1 Grid dba 8, Feb 20:57/dev/asm-diske BRW-RW----. 1 Grid dba 8, Feb 20:57/DEV/ASM-DISKF
When using SCSI disk: Cat/etc/udev/rules.d/99-oracle-asmdevices.rules kernel== "sd*", bus== "scsi", program== "/sbin/scsi_id"- Whitelisted--replace-whitespace--device=/dev/$name ", result==" ", Name=" ASM-DISKB ", owner=" grid ", group=" Asmadmin ", Mode= "0660" kernel== "sd*", bus== "scsi" program== "/sbin/scsi_id--whitelisted"--replace-whitespace--device=/dev/$ Name ", result==" ", Name=" ASM-DISKC ", owner=" grid ", group=" Asmadmin ", mode=" 0660 "kernel==" sd* ", bus==" scsi ", program== "/sbin/scsi_id--whitelisted--replace-whitespace--device=/dev/$name", result== "", Name= "ASM-DISKD", OWNER= "grid", Group= "Asmadmin", mode= "0660" kernel== "sd*", bus== "scsi" program== "/sbin/scsi_id--whitelisted"--replace-whitespace --device=/dev/$name ", result==" ", Name=" Asm-diske ", owner=" grid ", group=" Asmadmin ", mode=" 0660 "kernel==" sd* ", BUS==" SCSI, program== "/sbin/scsi_id--whitelisted--replace-whitespace--device=/dev/$name", result== "", NAME= "ASM-DISKF" , owner= "Grid", group= "Asmadmin", mode= "0660"
Disk UUID that does not correctly identify ASM disk
[Root@node2 dev]# ls-l/dev/asm* ls:cannot access/dev/asm*: No such file or directory
Very strange, the principle should be SCSI also see can be realized, but no, everyone in the test when the problem should be noticed.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.