[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
Thomas Schmitt
bugzilla_noreply at kde.org
Wed Nov 30 11:48:31 UTC 2016
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #46 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,
i am now looking into the source code of growisofs (file transport.hxx).
There is no interpretation of
sg_io_hdr_t.host_status
which in case of the cdrskin run bears the SG_ERR_DID_NO_CONNECT error
indicator.
So it could well be that growisofs just skips over this problem and
goes on with burning.
cdrecord-2.01.01a77/libscg/scsi-linux-sg.c seems to consider the error
to be retryable. I.e. cdrecord would go on, too. But i assume it would
repeat the WRITE command, which is different from what growisofs would do.
cdrecord prints the sg_io_hdr_t.host_status only if scgp->debug is set.
There is a cdrecord option
-d
which here triggers lots of messages of form
host_status: 00 driver_status: 08
It would be interesting to see the output file /tmp/cdrecord.log of this run:
dd if=/dev/zero bs=2048 count=375808 | /usr/bin/cdrecord -d -v -V gracetime=2
dev=/dev/sr1 speed=18 -sao driveropts=burnfree -data -tsize=375808s -
>/tmp/cdrecord.log 2>&1
----------------------------------------------------------------------------
Please check whether the growisofs and cdrecord written pseudo media contain
an exact copy of the input data. (I currently doubt because i suspect that
cdrecord repeats the ERITE command whereas growisofs does not.)
Maybe you first have to create an ISO image and then burn it to media in a
second K3B run, so that you can compare image file and media content.
If so, then i will try to develop a changeset for libburn which lets it
ignore this (normally severe) error for your testing purposes.
----------------------------------------------------------------------------
Regrettably i cannot find a Debian package which would provide a command
"cdemu". Can you give me some hints how to install it on a Linux VM ?
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the k3b
mailing list