From: "Thomas Schmitt" <scdbackup@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] k3b burning BD-Disk pretends to fail at 99.99%
Date: Sat, 13 Jul 2013 12:18:21 +0200 [thread overview]
Message-ID: <2958062521403394201@scdbackup.webframe.org> (raw)
In-Reply-To: <1480356.OfmO5JXGQV@zeus>
Hi,
> maybe the problem is when closing the session or writing some kind of lead-
> out, or the like.
The problem is that the CLOSE TRACK/SESSION command is appropriate
for the end of burning BD-R, only if it is unformatted or if it is
formatted to SRM without Pseudo Overwrite.
As soon as it is formatted to Pseudo Overwrite, the command is
inappropriate, which the burner indicates by the ILLEGAL REQUEST
error code (which one would see if K3b would not swallow it).
The bug of growisofs is that it formats the BD-R to Pseudo Overwrite
but omits to memorize this new state.
If the BD-R is already formatted to Pseudo Overwrite when growisofs
inspects it, then its state gets memorized and the inappropriate
SCSI command is not issued.
My patch proposal just sets the memorizing Pseudo Overwrite flag
after the medium has been formatted. So growisofs treats it the
same as if it had already been formatted when growisofs first
inspected it.
This avoids the error.
Have a nice day :)
Thomas
next prev parent reply other threads:[~2013-07-13 10:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 16:33 [gentoo-user] k3b burning BD-Disk pretends to fail at 99.99% Alexander Puchmayr
2013-07-06 21:55 ` Joerg Schilling
2013-07-07 12:06 ` Alexander Puchmayr
2013-07-07 16:31 ` Joerg Schilling
2013-07-08 6:53 ` Paul Colquhoun
2013-07-09 7:57 ` Mick
2013-07-10 5:29 ` Thomas Schmitt
2013-07-10 6:26 ` Dale
2013-07-10 7:23 ` Thomas Schmitt
2013-07-10 7:29 ` Dale
2013-07-10 7:46 ` Thomas Schmitt
2013-07-10 8:36 ` Joerg Schilling
2013-07-10 9:30 ` Thomas Schmitt
2013-07-10 9:46 ` Joerg Schilling
2013-07-13 6:16 ` Alexander Puchmayr
2013-07-13 10:18 ` Thomas Schmitt [this message]
2013-07-10 8:34 ` Joerg Schilling
2013-07-10 8:33 ` Joerg Schilling
2013-07-10 8:16 ` Joerg Schilling
2013-07-13 6:30 ` Alexander Puchmayr
2013-07-13 10:08 ` Thomas Schmitt
2013-07-13 11:43 ` Mick
2013-07-13 12:35 ` Thomas Schmitt
2013-07-13 13:03 ` Bruce Hill
2013-07-13 13:38 ` Thomas Schmitt
2013-07-13 16:38 ` Bruce Hill
2013-07-13 17:03 ` Thomas Schmitt
2013-07-13 17:30 ` Bruce Hill
2013-07-13 18:15 ` Thomas Schmitt
2013-07-13 21:25 ` Bruce Hill
2013-07-13 22:01 ` Thomas Schmitt
2013-07-14 14:20 ` Joerg Schilling
2013-07-14 14:08 ` Joerg Schilling
2013-07-14 13:52 ` Joerg Schilling
2013-07-14 11:32 ` Joerg Schilling
2013-07-10 7:57 ` Joerg Schilling
2013-07-10 8:42 ` Mick
2013-07-07 22:19 ` Paul Hartman
2013-07-08 7:40 ` Alexander Puchmayr
2013-07-08 10:51 ` Joerg Schilling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2958062521403394201@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox