virtio block devices names are not recycled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
I'm playing with eucalyptus, and attaching and detaching a block device as a virtio (bug 588410)
$ euca-attach-volume --instance ${inst} --device /dev/vdc ${vol}
VOLUME vol-5EC30651
Then,
$ euca-detach-volume ${vol}
The device names start as /dev/vda and go through to /dev/vdz and then to /dev/vdaa ...
The names are not recycled it would appear. In other buses (scsi) I'm used to the device name being recycled.
This can most likely be re-created without eucalyptus, using only kvm, but I dont' have those steps right at hand.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.34-4-virtual x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Tue Jun 8 21:29:41 2010
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
PciMultimedia:
ProcCmdLine: root=/dev/sda1 console=ttyS0
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
Changed in linux (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: |
added: kernel-needs-review kernel-uncat removed: needs-upstream-testing |
tags: |
added: kernel-candidate kernel-core kernel-reviewed removed: kernel-needs-review kernel-uncat |
tags: | removed: kernel-candidate |
Hi Scott,
If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]