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

[scdbackup at gmx.net]

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.
  scsidev: 'ATA:0,1,0'
  devname: 'ATA'
  scsibus: 0 target: 1 lun: 0
  wodim: No such file or directory. 
  Cannot open SCSI driver!
  For possible targets try 'wodim -scanbus'.
  For possible transport specifiers try 'wodim dev=help'.
  For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
  the wodim documentation.

Kernel 2.4.21, ide-scsi, hdc = sg0 = 0,0,0 , hde = sg1 = 0,1,0

As soon as the burn on dev=0,0,0 is finished, the -atip command
on dev=0,1,0 works flawlessly again.


It seems to be a cdrecord legacy.
While wodim was still burning to dev=0,0,0 i executed:

  $ cdrecord dev=0,1,0 -v -atip
  Cdrecord-ProDVD-Clone 2.01.01a22 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling
  TOC Type: 1 = CD-ROM
  scsidev: '0,1,0'
  scsibus: 0 target: 1 lun: 0
  cdrecord: Device or resource busy. Cannot open '/dev/sg0'. Cannot open SCSI driver.
  cdrecord: For possible targets try 'cdrecord -scanbus'.
  cdrecord: For possible transport specifiers try 'cdrecord dev=help'.


cdrskin does not allow libburn to touch /dev/sg0 when
dev=0,1,0 is explictely given and points to /dev/sg1.
So it has no problems with cdrecord or wodim using
/dev/sg0 simultaneously.


Some more test results:

While cdrskin burns on dev=0,1,0 (i.e. has /dev/sg1 open O_EXCL)
wodim can -atip, blank and burn dev=0,0,0

While cdrskin burns on dev=0,0,0 (i.e. has /dev/sg0 open O_EXCL)
wodim cannot -atip dev=0,1,0

While wodim burns on dev=0,1,0
wodim can -atip, blank and burn dev=0,0,0
  

Have a nice day :)

Thomas