wodim hangs in endless loop when using SCSI device syntax
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cdrkit (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
xcdroast hang when it should create its device database.
I could chase this back to wodim from cdrkit 9:1.1.6-1ubuntu1:
wodim dev=0,3,0 -v -checkdrive debug=999999
dev: '0,3,0' speed: -1 fs: 12582912 driveropts '(null)'
TOC Type: 1 = CD-ROM
scsidev: '0,3,0'
scsibus: 0 target: 3 lun: 0
usal__open() 0,3,0
WARNING: the deprecated pseudo SCSI syntax found as device specification.
Support for that may cease in the future versions of wodim. For now,
the device will be mapped to a block device file where possible.
Run "wodim --devices" for details.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... giving up.
As one can see 0,3,0 is not /dev/hda but /dev/scd0:
# lsscsi
[0:0:3:0] cd/dvd PLEXTOR CD-ROM PX-12TS 1.02 /dev/scd0
[0:0:5:0] cd/dvd TEAC CD-R58S 1.0H /dev/scd1
This makes at least xcdroast not work any more.
I do not know which other programs call wodim this way and are broken
if they are not already configured successfully.
And I do not know if using the wrong device node can cause data loss in other
configurations.
summary: |
- [gutsy] wodim hangs in endless loop when using SCSI device syntax + wodim hangs in endless loop when using SCSI device syntax |
Possibly related to bug 2765.