[Bug 631795] Re: Udev has a race condition with device mapper devices

[Tais Plougmann Hansen]

This sounds similar to what I experience.

On every cold boot, dmraid fails to create devices nodes for a secondary
software raid 1+0 device, which means that the "failed to mount, s to
skip mounting or m for manual recovery" message is shown. I have to hit
M, type dmraid -an, dmraid -ay and exit shell again to have the system
boot normally. (just typing dmraid -ay doesn't work - I have to
deactivate raid sets first.)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/631795

Title:
  Udev has a race condition with device mapper devices

Status in “linux” package in Ubuntu:
  Triaged
Status in “udev” package in Ubuntu:
  Triaged

Bug description:
  When using lvm and/or dmraid devices, often times during boot up udev
  prints messages like:

  udevd-work[72]: inotify_add_watch(6, /dev/dm-6, 10) failed: No such
  file or directory

  I believe this is caused by a race condition somewhere causing udev to
  attempt to access the newly created dm device before the dev node
  actually appears in /dev.  Sometimes it seems to get as far as running
  blkid before the dev node appears, causing it to fail to identify the
  UUID of the device and create the /dev/disk/by-uuid symlinks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/631795/+subscriptions