What should I do if the device id of the Linux virtual machine does not match the drive letter?

In the Linux virtual machine, the device id is the drive letter of the mapped disk, so the device id and the drive letter are consistent. However, when users look at the Linux device id, they find that the device id in the Linux virtual machine does not match the drive letter. What should I do at this time?

When a user mounts multiple scsi disks, the internal disk mapping and user configuration of the virtual machine are inconsistent after the Linux virtual machine is restarted. As shown in the figure, the virtual machine scsi device id configured by the user corresponds to the drive letter.

When restarting the virtual machine, the device id of a correspondence relationship scsi letter virtual machine configuration is inconsistent with the user. id scsi devices with virtual machine letter inconsistent shown below:

In this case, the corresponding letter Oracle RAC device used is changed, the service will cause some influences.

Solution:

The scsi device id needs to be specified when using the virtual machine scsi device. This solution is mainly used when the entire scsi disk is used and the scsi disk is not partitioned inside the virtual machine. Environment: RedHat 6.5 64-bit operating system, for example: /etc/udev/rules.d/60-raw.rules configuration file.

ACTION==“add”, KERNEL==“sd*”, PROGRAM==“/sbin/scsi_id -g -u -d /dev/$name”,

RESULT==“360022a11000e085d0de717f500000003”, RUN+=“/bin/raw /dev/raw/raw1 %N”

ACTION==“add”, KERNEL==“sd*” , PROGRAM==“/sbin/scsi_id -g -u -d /dev/$name”,

RESULT==“360022a11000e085d0de7372c0000002e”, RUN+=“/bin/raw /dev/raw/Raw2 %N”

KERNEL==“raw1”, OWNER=“grid”, GROUP=“oinstall”, MODE=“777”

KERNEL==“raw2&rdquo ;, OWNER=“grid”, GROUP=“oinstall”, MODE=“777” Previous12Next Total 2 Pages