Thanks to Soren Hansen for determining that /sys/module/nbd/parameters/max_part
was set to 0. I'm not sure if the module was getting loaded before my script
(which loads nbd with max_part=15) with the upstream default of '0' now and it
wasn't before, but this fixes it for me:
$ sudo rmmod nbd
$ sudo modprobe nbd max_part=15
** Changed in: nbd (Ubuntu)
Sourcepackagename: linux => nbd
Importance: Undecided => Wishlist
Status: New => Confirmed
** Summary changed:
- [jaunty] /dev/ndb0p* devices are no longer created/accessible
+ [jaunty] /sys/module/nbd/parameters/max_part is 0, which prevents /dev/nbd0p*
devices from getting created
--
[jaunty] /sys/module/nbd/parameters/max_part is 0, which prevents /dev/nbd0p*
devices from getting created
https://bugs.launchpad.net/bugs/342563
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
