[Debburn-devel] Trouble running wodim on dev=0, 0, 0 and dev=0, 1, 0 simultaneously

Eduard Bloch edi at gmx.de
Sat Dec 9 20:14:15 CET 2006


#include <hallo.h>
* Thomas Schmidt [Sat, Dec 09 2006, 06:43:44PM]:
> Hi,
> 
> i experience the effect that wodim is not willing
> to start work with drive dev=0,1,0 while another wodim
> instance is burning to dev=0,0,0 .
> 
> It complains about /dev/sg0 which corresponds to
> dev=0,0,0 and is unwilling to obtain usable info
> >from the drive that is /dev/sg1 resp. dev=0,1,0 .
> The drive tray does not get loaded.
> 
>   $ wodim dev=0,1,0 -v -atip
>   TOC Type: 1 = CD-ROM
>   scsidev: '0,1,0'
>   scsibus: 0 target: 1 lun: 0
>   Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second.
>   Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second.
>   Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second.
>   Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying in 1 second.
>   Error trying to open /dev/sg0 exclusively (Device or resource busy)... giving up.

cdrkit (1.0pre5) RELEASED; urgency=low

  [ Eduard Bloch ]
  ...
  * scsi-linux-sg.c: skipping unallowed devices, cleanup/consolidation of the
    old workaround(s) for ATA now for SCSI too

Which version are you using?
And what happens if you specify the device file instead of the
faked pseudo-SCSI numbers?

Eduard.
-- 
Zwei Reisende im Bahnabteil streiten:
"Das Fenster bleibt zu, sonst erfriere ich!"
"Das Fenster wird geöffnet, sonst ersticke ich!"
Sagt ein dritter:
"Darf ich schlichten? Lassen wir doch das Fenster zuerst zu, dann erstickt der
eine, dann machen wir's auf, dann erfriert der andere, und dann ist endlich
Ruhe!"



More information about the Debburn-devel mailing list