public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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:08:07 +0200	[thread overview]
Message-ID: <14437625216571153026@scdbackup.webframe.org> (raw)
In-Reply-To: <4789664.JvAW5a2jYR@zeus>

Hi,

> attemting to create a 
> BD-RE disk (Re-recordables are nice, sine non-RW media don't grow in my
> garden ;-)

Yeah. A BD-R tree would be a fine thing.

Note that growisofs on BD-RE would not show the bug at the end.
It happens only with BD-R which you submit in blank state.

If you treat your BD-R with dvd+rw-format before using them,
the bug should not show up.

If you can talk K3b into using growisofs option
  -use-the-force-luke=spare:none
then it will not format the blank BD-R, work with full nominal
speed, and should not show the bug. (There will be no Defect
Management. So there will be no checkreading and no replacement
of bad blocks.)

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

I wrote a mail to media-optical@gentoo.org, proposing the patch
for growisofs.
Regrettably there was no reaction yet.

Maybe if enough Gentoo users complain ...


Have a nice day :)

Thomas



  reply	other threads:[~2013-07-13 10:08 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
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 [this message]
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=14437625216571153026@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