[Bug 1127867] Re: /etc/udev/rules.d/65-mdadm.vol_id.rules uses non-existent 'vol_id'
Mathew Hodson
mathew.hodson at gmail.com
Thu Apr 16 23:08:00 UTC 2015
** Tags removed: removal-candidate
** Bug watch added: Debian Bug tracker #541884
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541884
** Also affects: mdadm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541884
Importance: Unknown
Status: Unknown
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1127867
Title:
/etc/udev/rules.d/65-mdadm.vol_id.rules uses non-existent 'vol_id'
Status in mdadm package in Ubuntu:
Fix Released
Status in mdadm source package in Lucid:
Confirmed
Status in mdadm source package in Oneiric:
Won't Fix
Status in mdadm source package in Precise:
Fix Released
Status in mdadm source package in Quantal:
Fix Released
Status in mdadm source package in Raring:
Fix Released
Status in mdadm package in Debian:
Unknown
Bug description:
[Impact]
* In Lucid, /etc/udev/rules.d/65-mdadm.vol_id.rules conffile was
dropped, but not properly removed in the preinst scripts. Later a
conffile removal was added, but it had a wrong file name.
* Causes errors to be printed on boot.
* The fix is to properly remove this conffile.... all the until next
LTS.
[Test Case]
* Install mdadm package in Hardy, upgrade to precise, observe that
the conffile is not removed.
* Upgrading to raring/SRU'ed package should remove this conffile.
[Regression Potential]
* Minimal as the conffile in question should not be used at boot.
[Original Description]
After upgrading a server from 10.04 to 12.04 I saw errors on boot about udev trying to use a non-existent vol_id:
failed to execute '/lib/udev/vol_id' 'vol_id --export /dev/md0': No such file or directory
I tracked this down to the following line in /etc/udev/rules.d/65-mdadm.vol_id.rules:
IMPORT{program}="vol_id --export $tempnode"
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541884 mentions this issue and says that we should be using '/sbin/blkid -o udev -p ...' instead. Indeed, checking /lib/udev/rules.d/64-md-raid.rules, it has:
IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
I then updated /etc/udev/rules.d/65-mdadm.vol_id.rules to use this
instead, and the errors went away.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1127867/+subscriptions
More information about the foundations-bugs
mailing list