The UNIX and Linux Forums  
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.

Go Back   The UNIX and Linux Forums > Special Forums > Hardware > Filesystems, Disks and Memory
Udev label removes corresponding fdisk, sfdisk or lsvdev entry Udev label removes corresponding fdisk, sfdisk or lsvdev entry
.
google unix.com

Forums Register Forum RulesLinksAlbums FAQ Members List Calendar Search Today's Posts Mark Forums Read


Filesystems, Disks and Memory Discuss NAS, SAN, RAID, Robotic Libraries, backup devices, RAM, DRAM, SCSI, IDE, EIDE topics here.

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
sfdisk for automated partitioning? alirezan Shell Programming and Scripting 0 08-22-2008 07:46 PM
Legal Ruling Removes Open-Source Cloud - CNNMoney.com iBot UNIX and Linux RSS News 0 08-13-2007 08:30 PM
Legal Ruling Removes Open-Source Cloud - Investor's Business Daily (subscription) iBot UNIX and Linux RSS News 0 08-13-2007 08:00 PM
Script removes itself kayarsenal Shell Programming and Scripting 5 09-08-2006 11:24 AM
udev core 5 GJ2 Linux 0 04-05-2006 03:29 AM

Closed Thread
English Japanese Spanish French German Portuguese Italian Dutch Swedish Russian Norwegian Hungarian Hebrew Danish Powered by Powered by Google
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old 03-02-2009
Radar's Avatar
Radar Radar is offline
Registered User
  
 

Join Date: Dec 2006
Location: Clifton Park, NY
Posts: 86
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.

Example udev rule:
Code:
# cat /etc/udev/rules.d/55-oracle-naming.rules
# Configure persistent, user-defined Oracle Clusterware device file names
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="3600a0b8000476694000004704974f509", NAME="ocr1", OWNER="root", GROUP="oinstall", MODE="0640"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="3600a0b80004793a2000004ae4974e92d", NAME="ocr2", OWNER="root", GROUP="oinstall", MODE="0640"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="3600a0b8000478034000003e04974f6f0", NAME="ocr3", OWNER="root", GROUP="oinstall", MODE="0640"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="3600a0b80004793da000004904974e9b1", NAME="vot1", OWNER="oracle", GROUP="oinstall", MODE="0640"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="3600a0b8000476694000004734974f778", NAME="vot2", OWNER="oracle", GROUP="oinstall", MODE="0640"
KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="3600a0b80004793a2000004b14974ea59", NAME="vot3", OWNER="oracle", GROUP="oinstall", MODE="0640"
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 udev labeled ones?

Thx
  #2 (permalink)  
Old 03-06-2009
otheus's Avatar
otheus otheus is offline Forum Staff  
Moderator ala Mode
  
 

Join Date: Feb 2007
Location: Innsbruck, Austria
Posts: 1,884
I cannot give you a 100% certainty that this will not fail, but I'm 98% certain that the scsi_id is unique and will always return the correct result and will faithfully identify the disk, even if the disks are move or renumbered.

Quote:
I'm just looking for how to explain this behavior.
redhat.com | Red Hat Magazine - Configuring Devices with udev
  #3 (permalink)  
Old 03-06-2009
Radar's Avatar
Radar Radar is offline
Registered User
  
 

Join Date: Dec 2006
Location: Clifton Park, NY
Posts: 86
Quote:
Originally Posted by otheus View Post
I cannot give you a 100% certainty that this will not fail, but I'm 98% certain that the scsi_id is unique and will always return the correct result and will faithfully identify the disk, even if the disks are move or renumbered.
You are correct. That's the method I use to verify that that block device is indeed still there, but just being referenced by the new label.

Interestingly, /proc/partitions will always show those six missing devices that udev labels, but reading from them via dd by that sd device name will fail.
Closed Thread

Bookmarks

« Creating filesystem of 2MB size | Performance Hit With Many Files »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Hybrid Mode Hybrid Mode
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -4. The time now is 12:59 AM.

The UNIX and Linux Forums - Learn UNIX and UNIX Commands RSS Feeds - Contact Us - The UNIX and Linux Forums - Learn UNIX and UNIX Commands - Archive - Top

Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited. Language Translations Powered by .
vBCredits v1.4 Copyright ©2007 - 2008, PixelFX Studios
The UNIX and Linux Forums Content Copyright ©1993-2009. All Rights Reserved.Ad Management by RedTyger

Content Relevant URLs by vBSEO 3.2.0