Bug 62565 - udev: 60-persistent-storage.rules ignores NBD
Summary: udev: 60-persistent-storage.rules ignores NBD
Status: VERIFIED NOTABUG
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-20 17:15 UTC by Marius Vollmer
Modified: 2013-03-22 07:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Vollmer 2013-03-20 17:15:45 UTC
I think a NBD device is just like any other block device, isn't it?  I was expecting it to have things like ID_FS_TYPE set on it.
Comment 1 Kay Sievers 2013-03-20 17:41:14 UTC
The nbd devices are set up loop devices, we first have dead device
nodes, then later we attach stuff behind them. At the time of the udev
creation event, nothing works at nbd devices.

Userspace has no idea when to probe for the device, or when stuff changes,
it needs proper kernel support for that to work, which is as far as I know
not existing.

It is currently blacklisted for that reason, and removing the blacklist
could only happen if the nbd kernel side is changed to send out events
like loop, dm, md are doing it.
Comment 2 Marius Vollmer 2013-03-20 17:49:41 UTC
(In reply to comment #1)
> The nbd devices are set up loop devices, we first have dead device
> nodes, then later we attach stuff behind them. At the time of the udev
> creation event, nothing works at nbd devices.

That, unfortunately, makes a lot of sense.  Thanks a lot for the explanation!
Comment 3 Kay Sievers 2013-03-20 17:54:02 UTC
It should be possible though, to fix that in the kernel. It should be
just a couple of lines, with uevent sending hooks at the right place.

People familiar with nbd should be able to do that pretty quickly.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.