Hi team, here's a new case about failure in mapping volumes to a VBS node because a non-block device file Exists on /dev.
Problem Symptom
A volume fails to be mapped to the VBS.
The error message indicates that the generated SCSI drive letter conflicts with the existing common file name and the status code are 50151408 or -151408.
Problem Diagnosis
1. Log in to the faulty VBS node as user root, and search for keyword is not a BLOCK device. The following error log is displayed:
[root@HN_0_0 run]# grep "is not a BLOCK device" /var/log/dsware/vbs/run/dsware_dsware_vbs_272.log[2019-11-01 14:44:19.403][15000029a0000][ERR][111897][scsi_initiator.c,291,check_dev_name][tid:0x7f2818954700][vbs:131073]ERROR! /dev/sda is not a BLOCK device!
If yes, go to 2.
If no, this fault is caused by other issues, and this document is not applicable.
2. Run the ls command to check whether the drive letter in the error log in Step 1 is a block device file.
root@HN_0_0 run]# ls -al /dev/sda-rw-------. 1 root root 0 Nov 1 14:45 /dev/sda
The first character in the first column of the ls command output indicates the file type. d indicates the directory, - indicates the file, l indicates the link file, b indicates the block device file, and c indicates the character device file.
If the file is a non-block device file, rectify the fault based on the following steps.
If the file is a block device file, the fault is caused by other issues, and this document is not applicable.
Causes
The /dev directory of the system is the device file directory. If a non-device file exists in the directory, when a volume is mapped to the VBS node, the corresponding device file is created in the /dev directory. If a file with the same name exists in the directory, the volume mapping fails to be created and an error message is displayed, indicating status code 50151408 or -151408.
Solution
Log in to the faulty VBS node as user root, move all non-block device files from the /dev directory to another directory, and map the volume to the VBS node again.
Before moving non-block device files in the /dev directory to another directory, you must obtain the customer's authorization. Notify the customer in advance and evaluate the effect scope of the operation.
Check After Recovery
After non-block device files are moved from the /dev directory to another directory,
the volume can be successfully mapped to the VBS node.
This is my solution, how about yours? Go ahead and share it with us!
