[jaunty] /sys/module/nbd/parameters/max_part is 0, which prevents /dev/nbd0p* devices from getting created
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Jaunty |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
Running Jaunty, I can no longer mount my qcow2 disk images via ndb because the /dev/nbd0p* devices don't get created.
Steps to reproduce (need a kvm VM):
1. sudo qemu-nbd --connect=/dev/nbd0 disk.img
2. $ sudo nbd-client -c /dev/nbd0
10350 (this shows it is available)
3. sudo fdisk -l /dev/nbd0
Disk /dev/nbd0: 5368 MB, 5368709120 bytes
4 heads, 32 sectors/track, 81920 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Disk identifier: 0x0005ae68
Device Boot Start End Blocks Id System
/dev/nbd0p1 1 62485 3999024 83 Linux
/dev/nbd0p2 62486 78110 1000000 82 Linux swap / Solaris
4. $ sudo mount /dev/nbd0p1 /mnt
mount: special device /dev/nbd0p1 does not exist
I'm putting this with linux, but it might be something else. Feel free to move it as needed. This was working up until yesterday.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType:
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux
Related branches
Changed in nbd: | |
importance: | Wishlist → Undecided |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Downgraded to udev 139-1 with no change.