Udev label removes corresponding fdisk, sfdisk or lsvdev entry
Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Udev label removes corresponding fdisk, sfdisk or lsvdev entry
I'm curious about the behavior where any udev labeled device causes that corresponding listing to disappear from fdisk, sfdisk, or in the case of RDAC, lsvdev.
I have seen this on both EMC clariion and Sun Storagetek/Engenio 6540 arrays.
We use RHEL5.1 and udev to create persistent labels for Oracle devices.
So the result in fdisk -l etc are that these 6 LUNS are missing, though the block devices are always accessible via the label.
I'm comfortable that we can always reference the /dev/ocr* or /dev/vot* devices, I'm just looking for how to explain this behavior. Is there some mechanism under the hood causing it? Is it so someone doesn't do things with those fdisk listed devices and inadvertently wipe out data on udev labeled ones?
[root@racmeta1 ~]# for i in sdt sdu sdw sdy sdaa sdac; do dd if=/dev/$i of=/dev/null bs=1M count=10; done
dd: opening `/dev/sdt': No such file or directory
dd: opening `/dev/sdu': No such file or directory
dd: opening `/dev/sdw': No such file or directory
dd: opening `/dev/sdy': No such file or directory
dd: opening `/dev/sdaa': No such file or directory
dd: opening `/dev/sdac': No such file or directory
[root@racmeta1 ~]# ls -l /dev/ocr* /dev/vot*
brw-r----- 1 root oinstall 65, 129 Mar 2 16:54 /dev/ocr1
brw-r----- 1 root oinstall 65, 49 Mar 2 16:54 /dev/ocr2
brw-r----- 1 root oinstall 65, 161 Mar 2 16:54 /dev/ocr3
brw-r----- 1 oracle oinstall 65, 65 Mar 3 09:47 /dev/vot1
brw-r----- 1 oracle oinstall 65, 193 Mar 3 09:47 /dev/vot2
brw-r----- 1 oracle oinstall 65, 97 Mar 3 09:47 /dev/vot3
[root@racmeta1 ~]# for i in `seq 1 3`; do dd if=/dev/ocr$i of=/dev/null bs=1M count=10; done
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.009242 seconds, 1.1 GB/s
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.009082 seconds, 1.2 GB/s
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.052977 seconds, 198 MB/s
[root@racmeta1 ~]# for i in `seq 1 3`; do dd if=/dev/vot$i of=/dev/null bs=1M count=10; done
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.220546 seconds, 47.5 MB/s
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.230579 seconds, 45.5 MB/s
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.236041 seconds, 44.4 MB/s
Last edited by TBC Cosmo; 03-03-2009 at 08:51 AM.
Reason: close code tag
Whilst I appreciate that you offered what you thought was useful, it isn't what I asked for nor need.
Actually it is, but I added what I know to be relevant, anticipating follow on questions. So it's not just for you to look at, it's actually for anyone else who cares to jump in and assist. But thanks anyway. Moving on...
/proc/partitions shows me the missing 6 devices from fdisk, as illustrated by the diff output. These devices are not accessible as named in /dev/. But scsi_id gives the unique ID and the udev labeled devices are accessible via their label in /dev. So back to the original question. What mechanism accounts for this behavior?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.