Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

The method of using udev persistence in Linux7 system Environment Software deployment Oracle RAC Cluster

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

This article mainly introduces the Linux7 system environment software deployment Oracle RAC cluster using udev persistence method, the article introduces in great detail, has a certain reference value, interested friends must read it!

In the linux6 version of the operating system, after configuring the udev configuration file, the udev binding disk persistence can be achieved by reloading the udev configuration file through start_udev. However, in the linux7 system, the start_udev command has been discarded, and the command cannot be found as follows:

[root@qsyxdb2 ~] # start_udevbash: start_udev: command not found. [root@qsyxdb2 ~] # cat / etc/redhat-release Red Hat Enterprise Linux Server release 7.3 (Maipo)

In linux7 systems, although there is no start_udev command, linux7 provides a more powerful and complete tool for udev management usage, namely udevadm, as shown below for help on using udevadm.

[root@qsyxdb2] # udevadm-helpudevadm [--help] [--version] [--debug] COMMAND [COMMAND OPTIONS] Send control commands or test the device manager. Commands: info Query sysfs or the udev database trigger Request events from the kernel settle Wait for pending udev events control Control the udev daemon monitor Listen to kernel and udev events test Test an event run test-builtin Test a built-in command [root@qsyxdb2 ~] #

Through the help information, you can view the detailed usage and the corresponding functions. You can study it by yourself according to your hobbies.

So how to achieve persistence through udev in linux7. After configuring udev, you need to execute udevadm trigger-- type=devices-- action=change or udevadm control-- reload or udevadm control-R to make the configuration file effective. As follows:

[root@qsyxdb2 ~] # cat / etc/udev/rules.d/99-oracle-asmdevices.rules KERNEL== "sd*", ENV {DEVTYPE} = = "disk", SUBSYSTEM== "block", PROGRAM== "/ usr/lib/udev/scsi_id-g-u-d $devnode", RESULT== "3600000e00d2a0000002a065a000b0000", RUN+= "/ bin/sh-c 'mknod / dev/asmdiskb b $major $minor; chown grid:asmadmin / dev/asmdiskb Chmod 0660 / dev/asmdiskb' "KERNEL==" sd* ", ENV {DEVTYPE} = =" disk ", SUBSYSTEM==" block ", PROGRAM==" / usr/lib/udev/scsi_id-g-u-d $devnode ", RESULT==" 3600000e00d2a0000002a065a000c0000 ", RUN+=" / bin/sh-c 'mknod / dev/asmdiskc b $major $minor; chown grid:asmadmin / dev/asmdiskc Chmod 0660 / dev/asmdiskc' "KERNEL==" sd* ", ENV {DEVTYPE} = =" disk ", SUBSYSTEM==" block ", PROGRAM==" / usr/lib/udev/scsi_id-g-u-d $devnode ", RESULT==" 3600000e00d2a0000002a065a000d0000 ", RUN+=" / bin/sh-c 'mknod / dev/asmdiskd b $major $minor; chown grid:asmadmin / dev/asmdiskd Chmod 0660 / dev/asmdiskd' "KERNEL==" sd* ", ENV {DEVTYPE} = =" disk ", SUBSYSTEM==" block ", PROGRAM==" / usr/lib/udev/scsi_id-g-u-d $devnode ", RESULT==" 3600000e00d2a0000002a065a00110000 ", RUN+=" / bin/sh-c 'mknod / dev/asmdiske b $major $minor; chown grid:asmadmin / dev/asmdiske Chmod 0660 / dev/asmdiske' "KERNEL==" sd* ", ENV {DEVTYPE} = =" disk ", SUBSYSTEM==" block ", PROGRAM==" / usr/lib/udev/scsi_id-g-u-d $devnode ", RESULT==" 3600000e00d2a0000002a065a00120000 ", RUN+=" / bin/sh-c 'mknod / dev/asmdiskf b $major $minor; chown grid:asmadmin / dev/asmdiskf Chmod 0660 / dev/asmdiskf' "[root@qsyxdb2 ~] # [root@qsyxdb2 ~] # sbin/udevadm trigger-- type=devices-- action=change [root@qsyxdb2 ~] # ll / dev/asmdisk*brw-rw---- 1 grid asmadmin 8, 16 August 16 15:35 / dev/asmdiskbbrw-rw---- 1 grid asmadmin 8, 32 August 16 15:35 / dev/asmdiskcbrw-rw---- 1 grid asmadmin 8, 48 August 16 15:35 / dev/asmdiskdbrw-rw---- 1 grid asmadmin 8 64 August 16 15:35 / dev/asmdiskebrw-rw---- 1 grid asmadmin 8, 80 August 16 15:35 / dev/asmdiskf

If the result does not take effect, then check the configuration file to make sure that the configuration file is configured correctly, but it will not take effect in the end, so you can only take a big step: restart the system.

These are all the contents of this article entitled "Linux7 system environment software deployment of Oracle RAC clusters using udev persistence". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report