Bug 158732 - devlabel do not remove symlinks to nonexisting (multipath) devices
devlabel do not remove symlinks to nonexisting (multipath) devices
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: devlabel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karel Zak
Depends On:
  Show dependency treegraph
Reported: 2005-05-25 07:02 EDT by Kari Hurtta
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-29 07:28:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
example (3.84 KB, text/plain)
2005-05-25 07:02 EDT, Kari Hurtta
no flags Details

  None (edit)
Description Kari Hurtta 2005-05-25 07:02:42 EDT
Description of problem:

devlabel reload do not remove symlinks to nonexiting devices.
It only prints 

The device /dev/sdg no longer seems to exist.  Because of this, the
symlink /dev/san/s1sanmsa1500_gomos -> /dev/sdg will not be available. The reference
to this symlink in /etc/sysconfig/devlabel will be ignored.

After reboot when devices are reassigned that symbol link
point to wrong device.

Version-Release number of selected component (if applicable):

[hurtta@smb2 hurtta]$ rpm -q devlabel
[hurtta@smb2 hurtta]$

How reproducible:

- make symlink to multipath device with devlabel
- make all paths to device fail
- reboot or run 'devlabel reload'
- notice that symlink is still kept.
Comment 1 Kari Hurtta 2005-05-25 07:02:42 EDT
Created attachment 114819 [details]
Comment 2 Karel Zak 2005-10-11 10:18:13 EDT
Please, I would like to see result of:

  cat /proc/partitions | awk {'print $1" "$2" "$3" "$4'}

before "devlabel reload" in situation when the path to device is not valid. 

By the way, devlabel reports many things (by syslog) to your system logs.
Comment 3 Radek Vokal 2006-11-29 07:28:08 EST
I'm closing this issue due to 1 year inactivity. Please reopen if you still
experience the described problems. 

Note You need to log in before you can comment on or make changes to this bug.