ITPUB论坛-中国最专业的IT技术社区

 找回密码
 注册
查看: 5413|回复: 9

oracle 11g r2 搭建rac遇到的共享磁盘问题,请帮忙看看是什么问题

[复制链接]
论坛徽章:
0
发表于 2017-1-5 10:33 | 显示全部楼层 |阅读模式
测试搭建oracle rac,平台是centos7,grid安装成功,asmca磁盘组创建成功,oracle数据库软件安装成功,当dbca创建数据库是遇到报错找不到‘DATA’磁盘。
[img]file:///C:/Users/Administrator/AppData/Roaming/Tencent/Users/1002738116/QQ/WinTemp/RichOle/Z4S8T804M[VXZ8J(S6JJ2QO.png[/img][img]file:///C:/Users/Administrator/AppData/Roaming/Tencent/Users/1002738116/QQ/WinTemp/RichOle/Z4S8T804M[VXZ8J(S6JJ2QO.png[/img]alert日志信息:
NOTE: Loaded library: System
ORA-15025: could not open disk "/dev/asm-data"
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
SUCCESS: diskgroup DATA was dismounted
ERROR: diskgroup DATA was not mounted
Errors in file /u01/app/oracle/diag/rdbms/rac/rac1/trace/rac1_ora_14792.trc:
ORA-00200: control file could not be created
ORA-00202: control file: '+DATA'
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15040: diskgroup is incomplete
ORA-1501 signalled during: CREATE DATABASE "rac"
从日志来看是权限问题,但在这个问题上卡了几天一直没能解决。

oracle用户:
[root@rac1 rac]# id oracle
uid=2101(oracle) gid=2000(oinstall) groups=2000(oinstall),2020(asmadmin),2021(asmdba),2031(dba),2032(oper)

grid用户:
[root@rac1 rac]# id grid
uid=2100(grid) gid=2000(oinstall) groups=2000(oinstall),2020(asmadmin),2021(asmdba),2022(asmoper),2031(dba),2032(oper)

asm磁盘组权限及所属用户和组     ----用的是udev绑定
[root@rac1 rac]# ll /dev/asm*
lrwxrwxrwx. 1 grid asmadmin 4 Jan  4 15:37 /dev/asm-data -> sdb1   ---这个是设置的DATA共享磁盘
lrwxrwxrwx. 1 grid asmadmin 4 Jan  4 15:37 /dev/asm-frm -> sdg1
lrwxrwxrwx. 1 grid asmadmin 4 Jan  4 15:37 /dev/asm-ocr -> sdf1
lrwxrwxrwx. 1 grid asmadmin 4 Jan  4 15:37 /dev/asm-orc -> sdc1
lrwxrwxrwx. 1 grid asmadmin 4 Jan  4 15:37 /dev/asm-orc1 -> sdd1
lrwxrwxrwx. 1 grid asmadmin 4 Jan  4 15:37 /dev/asm-vote -> sde1

[root@rac1 rac]# ll /dev/sd* ----绑定udev磁盘前格式化的
brw-rw----. 1 root disk 8,  0 Jan  4 13:35 /dev/sda
brw-rw----. 1 root disk 8,  1 Jan  4 13:35 /dev/sda1
brw-rw----. 1 root disk 8,  2 Jan  4 13:35 /dev/sda2
brw-rw----. 1 root disk 8, 16 Jan  4 13:35 /dev/sdb
brw-------. 1 grid root 8, 17 Jan  4 16:05 /dev/sdb1 -----不知道这个文件的权限及所属用户和组是否有影响(一直很疑惑),但改过777权限,grid:asmadmin也是不行
brw-rw----. 1 root disk 8, 32 Jan  4 13:35 /dev/sdc
brw-------. 1 grid root 8, 33 Jan  4 16:05 /dev/sdc1
brw-rw----. 1 root disk 8, 48 Jan  4 13:35 /dev/sdd
brw-------. 1 grid root 8, 49 Jan  4 15:37 /dev/sdd1
brw-rw----. 1 root disk 8, 64 Jan  4 13:35 /dev/sde
brw-------. 1 grid root 8, 65 Jan  4 16:05 /dev/sde1
brw-rw----. 1 root disk 8, 80 Jan  4 13:35 /dev/sdf
brw-------. 1 grid root 8, 81 Jan  4 15:37 /dev/sdf1
brw-rw----. 1 root disk 8, 96 Jan  4 13:35 /dev/sdg
brw-------. 1 grid root 8, 97 Jan  4 15:37 /dev/sdg1

oracle用户的oracle文件:   -----参照网上的解决办法更改的,但并没有成功(dbca建库时rac1节点的oracle文件会自动由组oinstall变成asmadmin ,但节点rac2不会需要手动改)
[root@rac2 /]# ll /u01/app/oracle/product/11.2.0/db_1/bin/oracle
-rwsr-s--x. 1 oracle asmadmin 239520784 Jan  3 15:18 /u01/app/oracle/product/11.2.0/db_1/bin/oracle

grid用户的oracle文件: -----无奈之下也曾试过把这个文件的组改成asmadmin,但依然不行。
[root@rac2 /]# ll /u01/app/11.2.0/grid/bin/oracle
-rwsrwsr-x. 1 grid oinstall 209854152 Jan  3 10:38 /u01/app/11.2.0/grid/bin/oracle

请大家帮忙看看到底是原因。

认证徽章
论坛徽章:
0
发表于 2017-1-6 11:48 | 显示全部楼层
问题解决了吗,以前我也出现过这种情况,你把/etc/udev/rules.d/60-raw.rules粘出来我看看

使用道具 举报

回复
论坛徽章:
0
 楼主| 发表于 2017-1-6 13:46 | 显示全部楼层
13791125320 发表于 2017-1-6 11:48
问题解决了吗,以前我也出现过这种情况,你把/etc/udev/rules.d/60-raw.rules粘出来我看看

问题还未解决
用的是udev绑定 uuid    ------环境是VMware虚拟机搭建的

[root@rac1 ~]# cat /etc/udev/rules.d/99-oracle-asmdevices.rules
KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c29a7007bc31073c6d3ecb1bb404",SYMLINK+="asm-data",OWNER="grid",GROUP='asmadmin",mode="0660"

KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c29e06ae342764b3b904656c7334",SYMLINK+="asm-orc",OWNER="grid",GROUP='asmadmin",mode="0660"

KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c29951b089c1e637a5aa4490cd74",SYMLINK+="asm-orc1",OWNER="grid",GROUP='asmadmin",mode="0660"

KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c2996d2485d3933655df62945a51",SYMLINK+="asm-vote",OWNER="grid",GROUP='asmadmin",mode="0660"
KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c29b941fd85caadc6266ad77b18c",SYMLINK+="asm-ocr",OWNER="grid",GROUP='asmadmin",mode="0660"

KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c291c1f0b015efa5088e2e072097",SYMLINK+="asm-frm",OWNER="grid",GROUP='asmadmin",mode="0660"

使用道具 举报

回复
论坛徽章:
0
发表于 2017-1-6 16:05 | 显示全部楼层

使用道具 举报

回复
论坛徽章:
0
 楼主| 发表于 2017-1-6 22:13 | 显示全部楼层
sysadm_cc 发表于 2017-1-6 16:05
http://blog.itpub.net/17252115/viewspace-1104341/

谢谢回答,首先说一下问题还是没有解决
文章我大概看了一下,
关于GRID(oracle binary)和RDBMS(oracle binary) 两个oracle文件的所属组和权限,这在之前已经尝试过多次,并没有解决问题。
但在ASM共享磁盘的权限上发现以前忽略的一个地方,今天下午又试验了几次发现了两个问题。

问题1:
我用的操作系统是centos7  ,从网上的一些资料发现centos7之前的操作系统版本(包括rhel等也是如此)创建的共享磁盘如下
[root@rac1 ~]# ll /dev/*asm*
brw-rw—- 1 grid asmadmin 8, 16 Apr 27 18:52 /dev/asm-diskb
brw-rw—- 1 grid asmadmin 8, 32 Apr 27 18:52 /dev/asm-diskc
brw-rw—- 1 grid asmadmin 8, 48 Apr 27 18:52 /dev/asm-diskd
这些ASM磁盘文件都块设备文件(文件类型是‘b’)

而我在centos7操作系统下创建的ASM磁盘文件如下
[root@rac1 ~]# ll /dev/asm*
lrwxrwxrwx. 1 root root 4 Jan  6 17:54 /dev/asm-data -> sdb1
lrwxrwxrwx. 1 root root 4 Jan  6 17:44 /dev/asm-ocr -> sdf1
ASM磁盘文件确是一个链接文件,文件所属用户和组也不对。
就此产生了一个疑问,是因为我udev绑定裸设备的时候规则配置错误导致的ASM磁盘成为了一个链接文件,还是centos7这个操作系统版本创建的ASM磁盘就是一个链接文件?

以下是udev绑定的规则:(其中一条)
KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c29a7007bc31073c6d3ecb1bb404",SYMLINK+="asm-data",OWNER="grid",GROUP='asmadmin",mode="0660"

问题2:(在centos7创建的ASM共享磁盘就是一个链接文件的基础上)
[root@rac1 ~]# ll /dev/asm*
lrwxrwxrwx. 1 root root 4 Jan  6 17:54 /dev/asm-data -> sdb1    -----ASM磁盘文件指向的是sdb1文件

[root@rac1 ~]# ll /dev/sd*
brw-rw----. 1 root disk 8,  0 Jan  6 17:42 /dev/sda
brw-rw----. 1 root disk 8,  1 Jan  6 17:42 /dev/sda1
brw-rw----. 1 root disk 8,  2 Jan  6 17:42 /dev/sda2
brw-rw----. 1 root disk 8, 16 Jan  6 17:42 /dev/sdb
brw-------. 1 grid root 8, 17 Jan  6 17:55 /dev/sdb1    -----这是分区和udev绑定裸设备之后的初始用户组和权限(是块设备文件)
从用户组和权限来看肯定是达不到需求的。
但在之前一直无法解决问题的无奈之下也曾把sdb1文件的用户和组设为 grid:asmadmin  权限设置为 777.但也一直报错。
今天下午dbca建库时才发现了问题。
建库前把 sdb1文件的用户和组设为 grid:asmadmin   权限为777,
当dbca建库报错时又看了一下sdb1文件的属性,发现用户组和权限又被修改成了初始时的值即用户和组为  grid:root,权限为600。

至于为什么会更改sdb1文件的所属组和权限却没有找到原因。

个人觉得一直报的权限错误大概就是这两个问题导致的,却无法确认也没找到解决的办法。
希望知道的能帮助解答一下这两个问题。

使用道具 举报

回复
认证徽章
论坛徽章:
0
发表于 2017-1-7 12:26 | 显示全部楼层
本帖最后由 13791125320 于 2017-1-7 12:27 编辑
sunjj_207 发表于 2017-1-6 22:13
谢谢回答,首先说一下问题还是没有解决
文章我大概看了一下,
关于GRID(oracle binary)和RDBMS(oracle  ...

你的grid能安装成功说明各种配置上基本上没有什么问题,我安装完grid,再往后遇见很多错误,有些也没有解决,但貌似都是跟权限有关,目录的权限,文件的所属用户,所属主,等等。我也重新安装了好几遍,下面的是我成功搭建rac的一些目录权限
mkdir -p /oracle/app
mkdir -p /oracle/app/oracle
mkdir -p /oracle/app/oracle/product/11.2.0/db_1
mkdir -p /oracle/app/grid
mkdir -p /oracle/app/11.2.0/grid
mkdir -p /oracle/app/oraInventory

chown -R oracleinstall /oracle
chmod -R 775 /oracle

chown -R oracleinstall /oracle/app
chmod -R 775 /oracle/app

chown oracleinstall /oracle/app/oracle
chmod -R 775 /oracle/app/oracle

chown oracleinstall /oracle/app/oracle/product/11.2.0/db_1
chmod -R 775 /oracle/app/oracle/product/11.2.0/db_1

chown -R gridinstall /oracle/app/grid
chmod -R 775 /oracle/app/grid

chown -R gridinstall /oracle/app/11.2.0/grid
chmod -R 775 /oracle/app/11.2.0/grid

chown gridinstall /oracle/app/oraInventory
chmod -R 775 /oracle/app/oraInventory


重点是这个:oracle用户
chmod 6751 $ORACLE_HOME/bin/oracle
chown oracleinstall $ORACLE_HOME/bin/oracle

使用道具 举报

回复
论坛徽章:
0
 楼主| 发表于 2017-1-9 17:23 | 显示全部楼层
问题已经解决了,
是udev绑定asm磁盘时,规则因粗心大意写错了导致的错误
KERNEL=="sd?1",SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",
RESULT=="36000c29a7007bc31073c6d3ecb1bb404",SYMLINK+="asm-data",OWNER="grid",GROUP='asmadmin",mode="0660"
错误1:
asmadmin的双引号前面的写成了单引号,
错误2:
mode应该是大写    ---两个错误一起发现的,是否必须大写倒没有认证过。

就是因为这两个错误导致sdb1块设备文件的权限以及所属组错误,
brw-rw----. 1 root disk 8, 16 Jan  6 17:42 /dev/sdb
brw-------. 1 grid root 8, 17 Jan  6 17:55 /dev/sdb1    ----错误的权限和所属组。

brw-rw----. 1 root disk     8, 16 Jan  9 13:57 /dev/sdb
brw-rw----. 1 grid asmadmin 8, 17 Jan  9 14:06 /dev/sdb1   ----正确的权限和所属组。
brw-rw----. 1 root disk     8, 32 Jan  9 13:57 /dev/sdc
brw-rw----. 1 grid asmadmin 8, 33 Jan  9 14:24 /dev/sdc1

错误更改之后,可以正常安装了,当时检查时不知为什么就是没有看到这么明显的错误。

使用道具 举报

回复
认证徽章
论坛徽章:
10
青年奥林匹克运动会-高尔夫
日期:2014-09-10 14:54:51火眼金睛
日期:2017-02-06 01:02:33人气徽章
日期:2016-11-09 15:56:29目光如炬
日期:2016-10-30 22:00:00罗罗诺亚·索隆
日期:2016-10-17 12:26:14目光如炬
日期:2016-10-16 22:00:00火眼金睛
日期:2016-11-30 22:00:00目光如炬
日期:2017-01-22 22:00:00美羊羊
日期:2015-04-12 10:40:59火眼金睛
日期:2017-02-28 22:00:00
发表于 2017-1-15 00:16 | 显示全部楼层
多借助工具检查

使用道具 举报

回复
认证徽章
论坛徽章:
4
慢羊羊
日期:2015-03-04 14:55:272015年新春福章
日期:2015-03-06 11:59:47秀才
日期:2015-08-06 10:47:08奥运会纪念徽章:摔跤
日期:2016-08-23 21:41:00
发表于 2017-3-31 11:18 | 显示全部楼层
sunjj_207 发表于 2017-1-9 17:23
问题已经解决了,
是udev绑定asm磁盘时,规则因粗心大意写错了导致的错误
KERNEL=="sd?1",SUBSYSTEM=="bl ...

你好,我在搭建的时候,也遇到了问题。udev跟你写的一样,但是却无法生成asm的设备。
报错如下:但是我看不懂,对udev还是不太懂
  1. [root@node1 dev]# udevadm test /sys/block/sdb
  2. calling: test
  3. version 219
  4. This program is for debugging only, it does not run any program
  5. specified by a RUN key. It may show incorrect results, because
  6. some values may be different, or not available at a simulation run.

  7. === trie on-disk ===
  8. tool version:          219
  9. file size:         7289802 bytes
  10. header size             80 bytes
  11. strings            1888554 bytes
  12. nodes              5401168 bytes
  13. Load module index
  14. Created link configuration context.
  15. timestamp of '/etc/udev/rules.d' changed
  16. Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
  17. Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
  18. Reading rules file: /usr/lib/udev/rules.d/11-dm-mpath.rules
  19. Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
  20. Reading rules file: /usr/lib/udev/rules.d/40-libgphoto2.rules
  21. IMPORT found builtin 'usb_id --export %%p', replacing /usr/lib/udev/rules.d/40-libgphoto2.rules:11
  22. Reading rules file: /usr/lib/udev/rules.d/40-redhat.rules
  23. Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
  24. Reading rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules
  25. Reading rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
  26. Reading rules file: /usr/lib/udev/rules.d/50-rbd.rules
  27. Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
  28. Reading rules file: /usr/lib/udev/rules.d/56-hpmud.rules
  29. Reading rules file: /usr/lib/udev/rules.d/60-alias-kmsg.rules
  30. Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
  31. Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
  32. Reading rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
  33. Reading rules file: /usr/lib/udev/rules.d/60-keyboard.rules
  34. Reading rules file: /usr/lib/udev/rules.d/60-net.rules
  35. Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
  36. Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
  37. Reading rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
  38. Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
  39. Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
  40. Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
  41. Reading rules file: /usr/lib/udev/rules.d/60-raw.rules
  42. Reading rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
  43. Reading rules file: /usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules
  44. Reading rules file: /usr/lib/udev/rules.d/61-gnome-settings-daemon-rfkill.rules
  45. Reading rules file: /usr/lib/udev/rules.d/62-multipath.rules
  46. Reading rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
  47. Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
  48. Reading rules file: /usr/lib/udev/rules.d/65-libwacom.rules
  49. Reading rules file: /usr/lib/udev/rules.d/65-md-incremental.rules
  50. Reading rules file: /usr/lib/udev/rules.d/65-sane-backends.rules
  51. Reading rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
  52. Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
  53. Reading rules file: /usr/lib/udev/rules.d/69-libmtp.rules
  54. Reading rules file: /usr/lib/udev/rules.d/69-xorg-vmmouse.rules
  55. Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
  56. Reading rules file: /etc/udev/rules.d/70-persistent-ipoib.rules
  57. Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
  58. Reading rules file: /usr/lib/udev/rules.d/70-printers.rules
  59. Reading rules file: /usr/lib/udev/rules.d/70-spice-vdagentd.rules
  60. Reading rules file: /usr/lib/udev/rules.d/70-touchpad-quirks.rules
  61. Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
  62. Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
  63. Reading rules file: /usr/lib/udev/rules.d/70-wacom.rules
  64. Reading rules file: /usr/lib/udev/rules.d/71-biosdevname.rules
  65. Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
  66. Reading rules file: /usr/lib/udev/rules.d/73-idrac.rules
  67. Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
  68. Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
  69. Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
  70. Reading rules file: /usr/lib/udev/rules.d/75-tty-description.rules
  71. Reading rules file: /usr/lib/udev/rules.d/77-mm-cinterion-port-types.rules
  72. Reading rules file: /usr/lib/udev/rules.d/77-mm-dell-port-types.rules
  73. Reading rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
  74. Reading rules file: /usr/lib/udev/rules.d/77-mm-haier-port-types.rules
  75. Reading rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
  76. Reading rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
  77. Reading rules file: /usr/lib/udev/rules.d/77-mm-mtk-port-types.rules
  78. Reading rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
  79. Reading rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules
  80. Reading rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules
  81. Reading rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
  82. Reading rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
  83. Reading rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules
  84. Reading rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules
  85. Reading rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
  86. Reading rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
  87. Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
  88. Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
  89. Reading rules file: /usr/lib/udev/rules.d/80-kvm.rules
  90. Reading rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
  91. Reading rules file: /usr/lib/udev/rules.d/80-net-name-slot.rules
  92. Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules
  93. Reading rules file: /usr/lib/udev/rules.d/80-udisks2.rules
  94. Reading rules file: /usr/lib/udev/rules.d/81-kvm-rhel.rules
  95. Reading rules file: /usr/lib/udev/rules.d/84-nm-drivers.rules
  96. Reading rules file: /usr/lib/udev/rules.d/85-nm-unmanaged.rules
  97. Reading rules file: /usr/lib/udev/rules.d/85-regulatory.rules
  98. Reading rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
  99. Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
  100. Reading rules file: /usr/lib/udev/rules.d/90-alsa-tools-firmware.rules
  101. Reading rules file: /usr/lib/udev/rules.d/90-iprutils.rules
  102. Reading rules file: /usr/lib/udev/rules.d/90-libgpod.rules
  103. Reading rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
  104. Reading rules file: /usr/lib/udev/rules.d/90-vconsole.rules
  105. Reading rules file: /usr/lib/udev/rules.d/91-drm-modeset.rules
  106. Reading rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
  107. Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
  108. Reading rules file: /usr/lib/udev/rules.d/95-udev-late.rules
  109. Reading rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
  110. Reading rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
  111. Reading rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
  112. Reading rules file: /usr/lib/udev/rules.d/98-kexec.rules
  113. Reading rules file: /usr/lib/udev/rules.d/98-rdma.rules
  114. Reading rules file: /usr/lib/udev/rules.d/98-trace-cmd.rules
  115. Reading rules file: /etc/udev/rules.d/99-my-asmdevices.rules
  116. Reading rules file: /usr/lib/udev/rules.d/99-qemu-guest-agent.rules
  117. Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
  118. rules contain 393216 bytes tokens (32768 * 12 bytes), 39893 bytes strings
  119. 32453 strings (273512 bytes), 28930 de-duplicated (237143 bytes), 3524 trie nodes used
  120. GROUP 6 /usr/lib/udev/rules.d/50-udev-default.rules:52
  121. IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/56-hpmud.rules:10
  122. unable to access usb_interface device of '/sys/devices/pci0000:00/0000:00:11.0/0000:02:07.0/host33/target33:0:1/33:0:1:0/block/sdb'
  123. IMPORT builtin 'usb_id' returned non-zero
  124. IMPORT 'scsi_id --export --whitelisted -d /dev/sdb' /usr/lib/udev/rules.d/60-persistent-storage.rules:50
  125. starting 'scsi_id --export --whitelisted -d /dev/sdb'
  126. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_SCSI=1'
  127. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_VENDOR=VMware_'
  128. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_VENDOR_ENC=VMware\x2c\x20'
  129. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_MODEL=VMware_Virtual_S'
  130. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_MODEL_ENC=VMware\x20Virtual\x20S'
  131. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_REVISION=1.0'
  132. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_TYPE=disk'
  133. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_SERIAL=36000c29ab15e8805b4b5a2c7256480f2'
  134. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_SERIAL_SHORT=6000c29ab15e8805b4b5a2c7256480f2'
  135. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_WWN=0x6000c29ab15e8805'
  136. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_WWN_VENDOR_EXTENSION=0xb4b5a2c7256480f2'
  137. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_WWN_WITH_EXTENSION=0x6000c29ab15e8805b4b5a2c7256480f2'
  138. 'scsi_id --export --whitelisted -d /dev/sdb'(out) 'ID_SCSI_SERIAL=6000c29ab15e8805b4b5a2c7256480f2'
  139. 'scsi_id --export --whitelisted -d /dev/sdb' [11174] exit with return code 0
  140. LINK 'disk/by-id/scsi-36000c29ab15e8805b4b5a2c7256480f2' /usr/lib/udev/rules.d/60-persistent-storage.rules:52
  141. IMPORT builtin 'path_id' /usr/lib/udev/rules.d/60-persistent-storage.rules:65
  142. LINK 'disk/by-path/pci-0000:02:07.0-scsi-0:0:1:0' /usr/lib/udev/rules.d/60-persistent-storage.rules:66
  143. IMPORT builtin 'blkid' /usr/lib/udev/rules.d/60-persistent-storage.rules:82
  144. probe /dev/sdb raid offset=0
  145. LINK 'disk/by-id/wwn-0x6000c29ab15e8805b4b5a2c7256480f2' /usr/lib/udev/rules.d/60-persistent-storage.rules:92
  146. no db file to read /run/udev/data/+scsi:33:0:1:0: No such file or directory
  147. handling device node '/dev/sdb', devnum=b8:16, mode=0660, uid=0, gid=6
  148. set permissions /dev/sdb, 060660, uid=0, gid=6
  149. preserve already existing symlink '/dev/block/8:16' to '../sdb'
  150. found 'b8:16' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fscsi-36000c29ab15e8805b4b5a2c7256480f2'
  151. creating link '/dev/disk/by-id/scsi-36000c29ab15e8805b4b5a2c7256480f2' to '/dev/sdb'
  152. preserve already existing symlink '/dev/disk/by-id/scsi-36000c29ab15e8805b4b5a2c7256480f2' to '../../sdb'
  153. found 'b8:16' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fwwn-0x6000c29ab15e8805b4b5a2c7256480f2'
  154. creating link '/dev/disk/by-id/wwn-0x6000c29ab15e8805b4b5a2c7256480f2' to '/dev/sdb'
  155. preserve already existing symlink '/dev/disk/by-id/wwn-0x6000c29ab15e8805b4b5a2c7256480f2' to '../../sdb'
  156. found 'b8:16' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fpci-0000:02:07.0-scsi-0:0:1:0'
  157. creating link '/dev/disk/by-path/pci-0000:02:07.0-scsi-0:0:1:0' to '/dev/sdb'
  158. preserve already existing symlink '/dev/disk/by-path/pci-0000:02:07.0-scsi-0:0:1:0' to '../../sdb'
  159. created db file '/run/udev/data/b8:16' for '/devices/pci0000:00/0000:00:11.0/0000:02:07.0/host33/target33:0:1/33:0:1:0/block/sdb'
  160. .ID_FS_TYPE_NEW=
  161. ACTION=add
  162. DEVLINKS=/dev/disk/by-id/scsi-36000c29ab15e8805b4b5a2c7256480f2 /dev/disk/by-id/wwn-0x6000c29ab15e8805b4b5a2c7256480f2 /dev/disk/by-path/pci-0000:02:07.0-scsi-0:0:1:0
  163. DEVNAME=/dev/sdb
  164. DEVPATH=/devices/pci0000:00/0000:00:11.0/0000:02:07.0/host33/target33:0:1/33:0:1:0/block/sdb
  165. DEVTYPE=disk
  166. ID_BUS=scsi
  167. ID_FS_TYPE=
  168. ID_MODEL=VMware_Virtual_S
  169. ID_MODEL_ENC=VMware\x20Virtual\x20S
  170. ID_PART_TABLE_TYPE=dos
  171. ID_PATH=pci-0000:02:07.0-scsi-0:0:1:0
  172. ID_PATH_TAG=pci-0000_02_07_0-scsi-0_0_1_0
  173. ID_REVISION=1.0
  174. ID_SCSI=1
  175. ID_SCSI_SERIAL=6000c29ab15e8805b4b5a2c7256480f2
  176. ID_SERIAL=36000c29ab15e8805b4b5a2c7256480f2
  177. ID_SERIAL_SHORT=6000c29ab15e8805b4b5a2c7256480f2
  178. ID_TYPE=disk
  179. ID_VENDOR=VMware_
  180. ID_VENDOR_ENC=VMware\x2c\x20
  181. ID_WWN=0x6000c29ab15e8805
  182. ID_WWN_VENDOR_EXTENSION=0xb4b5a2c7256480f2
  183. ID_WWN_WITH_EXTENSION=0x6000c29ab15e8805b4b5a2c7256480f2
  184. MAJOR=8
  185. MINOR=16
  186. MPATH_SBIN_PATH=/sbin
  187. SUBSYSTEM=block
  188. TAGS=:systemd:
  189. USEC_INITIALIZED=35804
  190. Unload module index
  191. Unloaded link configuration context.
复制代码

使用道具 举报

回复
认证徽章
论坛徽章:
4
慢羊羊
日期:2015-03-04 14:55:272015年新春福章
日期:2015-03-06 11:59:47秀才
日期:2015-08-06 10:47:08奥运会纪念徽章:摔跤
日期:2016-08-23 21:41:00
发表于 2017-3-31 11:30 | 显示全部楼层
我的rules的配置:
  1. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c29ab15e8805b4b5a2c7256480f2", SYMLINK+="asm_ocr_1_1",   OWNER="grid",  GROUP="asmadmin", MODE="0660"
  2. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c29f279d58ffbfb0465b6126b1c8", SYMLINK+="asm_ocr_2_1",   OWNER="grid",  GROUP="asmadmin", MODE="0660"
  3. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c2964e4e9ebbddf324e5ce4a8125", SYMLINK+="asm_ocr_3_1",   OWNER="grid",  GROUP="asmadmin", MODE="0660"
  4. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c290b96956c704b8a13fedf3a744", SYMLINK+="asm_vote_1_1",  OWNER="grid",  GROUP="asmadmin", MODE="0660"
  5. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c292ad2c0608d74eb8f7fc1f7156", SYMLINK+="asm_vote_2_1",  OWNER="grid",  GROUP="asmadmin", MODE="0660"
  6. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c295063c81ef49869ed6ac0e4911", SYMLINK+="asm_vote_3_1",  OWNER="grid",  GROUP="asmadmin", MODE="0660"
  7. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c29603ff7ca95246aeaeae3b9a3b", SYMLINK+="asm_data_1_1",  OWNER="grid",  GROUP="asmadmin", MODE="0660"
  8. KERNEL=="sd?1", SUBSYSTEM=="block",PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent",RESULT=="36000c29ee1ad1d769a9dca1709ad4e8e", SYMLINK+="asm_back_1_1",  OWNER="grid",  GROUP="asmadmin", MODE="0660"
复制代码

使用道具 举报

回复

您需要登录后才可以回帖 登录 | 注册

本版积分规则

TOP技术积分榜 社区积分榜 徽章 电子杂志 团队 统计 虎吧 老博客 知识索引树 读书频道 积分竞拍 文本模式 帮助
  ITPUB首页 | ITPUB论坛 | 数据库技术 | 企业信息化 | 开发技术 | 微软技术 | 软件工程与项目管理 | IBM技术园地 | 行业纵向讨论 | IT招聘 | IT文档 | IT博客
  ChinaUnix | ChinaUnix博客 | ChinaUnix论坛 | SAP ERP系统
CopyRight 1999-2011 itpub.net All Right Reserved. 北京皓辰网域网络信息技术有限公司版权所有 联系我们 网站律师 隐私政策 知识产权声明
京ICP证:060528号 北京市公安局海淀分局网监中心备案编号:1101082001 广播电视节目制作经营许可证:编号(京)字第1149号
  
快速回复 返回顶部 返回列表