Comment 5 for bug 244926
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Pasted relevant bit of the diff above, it's actually one of those new LP package version-to-version diffs, though it appears to have picked a larger diff than it needed to.
Fundamentally we call udevadm settle after vol_id to guarantee that udev has actually finished with the block device. This means we check:
1) the device exists, ie. udev has created it
2) vol_id returns valid data for the filesystem, ie. any lvm or mdadm has been activated
3) udev has settled, ie. any binaries run by udev have exited and there are no locks