Shulou(Shulou.com)06/01 Report--

Your environment is as follows:

[root@syk1 ~] # ll / dev/mapper/*crw-rw---- 1 root root 10, 58 Oct 24 07:59 / dev/mapper/controllrwxrwxrwx 1 root root 7 Oct 26 09:19 / dev/mapper/dg->.. / dm-0lrwxrwxrwx 1 root root 7 Oct 26 09:19 / dev/mapper/ocr->.. / dm-1 [root@syk1 ~] # ll / dev/dm-*brw-rw---- 1 grid asmadmin 253 0 Oct 26 09:43 / dev/dm-0brw-rw---- 1 grid asmadmin 253 1 Oct 26 09:43 / dev/dm-1 [root@syk1 ~] # more / etc/multipath.conf defaults {user_friendly_names yesmax_fds maxqueue_without_daemon noflush_on_last_del yes} multipaths {multipath {wwid 14f504e46494c4552736437624e562d55494b362d5130656e alias ocr} multipath { Wwid 14f504e46494c45525742544e57792d3349514d2d5472315a alias dg}} [root@syk1 ~] # more / etc/udev/rules.d/12-dm-permissions.rules 60-raw.rules 90-alsa.rules 98-kexec.rules 60-fprint-autosuspend.rules 70-persistent-cd.rules 90-hal.rules 99-fuse.rules 60-pcmcia.rules 70-persistent-net.rules 97-bluetooth-serial.rules [root@syk1 ~] # more / etc/udev/rules.d/12-dm-permissions.rules ENV {DM_NAME} = = "dg" OWNER:= "grid", GROUP:= "asmadmin", MODE:= "0660", SYMLINK+= "iscsi/oraasm-$env {DM_NAME}" ENV {DM_NAME} = = "ocr", OWNER:= "grid", GROUP:= "asmadmin", MODE:= "0660", SYMLINK+= "iscsi/oraasm-$env {DM_NAME}"

Reprint a post: about the binding of RAC permissions in RHEL6 installation

Red Hat Enterprise Linux 6.0 begins to deprecate the mode, uid, and gid parameters in the / etc/multipath.conf configuration file. The permissions of device-mapper devices (including multipath mapping) are set by udev rules. In the process of installing RAC, the granting of permissions is a troublesome problem. Generally speaking, whether it is RHEL5 or RHEL6, we will use UDEV to control permissions. Here are two ways to control disk permissions under RHEL6.

Method 1:

If you are using the multipathing software that comes with linux, we can use the following:

There is a template file in / usr/share/doc/device-mapper-version called 12-dm-permissions.rules, which we can use and put in the / etc/udev/rules.d directory to make it effective

The main purpose is to modify the following, such as:

ENV {DM_NAME} = "mpatha", OWNER:= "grid", GROUP:= "oinstall", MODE:= "660"

If an alias is specified for a multipath device, such as / etc/multipath.conf configuration is as follows

Multipath {

Wwid 360050763008101d4e00000000000000a

Alias ocr

In 12-dm-permissions.rules, you need to replace the default mpath* with an alias, such as:

ENV {DM_NAME} = "ocr", OWNER:= "grid", GROUP:= "oinstall", MODE:= "660"

After the configuration is completed, execute udevadm trigge to make the configuration effective. If not, use start_udev again.

[root@rac1 ~] # udevadm trigger

Check whether the dm device permissions are correct

[root@rac1 rules.d] # ll / dev/dm*

Method 2:

If you are using multipathing software that comes with storage, such as HDS storage multipathing software:

Is used in / etc/udev/rules.d/99-oracle-asmdevices.rules

KERNEL== "sddlmac*", OWNER= "grid", GROUP= "oinstall", MODE= "0660"

KERNEL== "sddlmaa*", OWNER= "grid", GROUP= "oinstall", MODE= "0660"

KERNEL== "sddlmab*", OWNER= "grid", GROUP= "oinstall", MODE= "0660"

If you use the multipath software DM-Multipath that comes with Linux, you need to obtain the UUID number that is stored on the device:

For example, we created the following devices through multipath:

Ocrvote1p1 ocrvote2p1 ocrvote3p1 db1p1 db2p1 frap1 redop1

Get the UUID with the following command:

# for i in ocrvote1p1 ocrvote2p1 ocrvote3p1 db1p1 db2p1 frap1 redop1; do

Printf "% s% s\ n"$I" $(udevadm info-- query=all-- name=/dev/mapper/$i |

Grep-I dm_uuid) "; done

The results are similar to the following:

Ocrvote1p1 E: DM_UUID=part1-mpath-3600c0ff000dabfe596a0f65101000000

Ocrvote2p1 E: DM_UUID=part1-mpath-3600c0ff000dabfe5a2a0f65101000000

Ocrvote3p1 E: DM_UUID=part1-mpath-3600c0ff000dabfe5b4a0f65101000000

Db1p1 E: DM_UUID=part1-mpath-3600c0ff000d7e7a854a0f65101000000

Db2p1 E: DM_UUID=part1-mpath-3600c0ff000dabfe562a0f65101000000

Frap1 E: DM_UUID=part1-mpath-3600c0ff000d7e7a874a0f65101000000

Redop1 E: DM_UUID=part1-mpath-3600c0ff000dabfe585a0f65101000000

So we make the following edits under / etc/udev/rules.d/99-oracle-asmdevices.rules:

KERNEL== "dm-*", ENV {DM_UUID} = = "part1-mpath-3600c0ff000dabfe5f4d8515101000000", OWNER= "grid", GROUP= "oinstall", MODE= "0660"

Add each of the above messages

In both of the above ways, we can bind multipath device permissions and ensure that there is no change.

It is recommended to use the multipath software that comes with storage.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.