[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Thomas Schmitt]

https://bugs.kde.org/show_bug.cgi?id=137436

--- Comment #70 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,

https://bugs.kde.org/attachment.cgi?id=102637
shows a failure around the same address (70+ MiB) as with cdrskin-1.4.6
but with a different reason. This time the ioctl(SG_IO) returned error
indication and errno says that the device was gone:

> cdrskin: ( Most recent system error: 19  'No such device' )
> --- SG_IO: return= -1 , errno= 19 , host_status= 0x0 , driver_status= 0x0

Maybe you find some messages about this event in your local system log.

------------------------------------------------------------------------

The only other indication of strangeness are diagnostic replies (Sense Data)
from the drive
> WRITE(10)
> 2a 00 00 00 88 40 00 00 10 00
> +++ sense data = 70 00 00 00 00 00 00 0A 00 00 00 00 00 15 00 00 00 00
> +++ key=0  asc=00h  ascq=15h

Key 0 is in SPC-3, table 27 described by the funny name "NO SENSE" and
"Indicates that there is no specific sense key information to be reported".
The error code combination ASC 0, ASCQ 15 is listed in SPC-3, table 28 as
"NO CURRENT AUDIO STATUS TO RETURN".
MMC-5, annex F lists ASC = 0 with ASCQ 00, 06, 16, or 17, but not 15.

------------------------------------------------------------------------

The statistical evidence is sparse. Hard to say whether it is just bad
luck that cdrskin gets hit or whether it teases the CDEmu code in some way.
It is not even clear whether the failures underneath K3B and the success
on the command line is of any significance.

(I once spent two days with trying to find out why libburn failed with
a particular drive and DVD-RW where growisofs succeeded. On the third day
growisofs started to fail and libburn succeeded. It was just a matter of
luck on a flaky combination of hardware.)

------------------------------------------------------------------------

For now i have no other proposal than to keep the CDEmu tests below 70 MB
of burn size and to later test larger sizes with a real DVD burner.

Have a nice day :)

Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.