public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] k3b burning BD-Disk pretends to fail at 99.99%
Date: Mon, 8 Jul 2013 12:51:44 +0200	[thread overview]
Message-ID: <51da99c0.76yYmzUYur0m8Fl0%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <2239745.sVKpviFgIl@zeus>

Alexander Puchmayr <alexander.puchmayr@linznet.at> wrote:

> > I don't use k3b but I know when I burn a 25GB disc image using
> > growisofs, I have to disable the spare sectors otherwise it won't fit
> > on the disc, and it burns all the way until the end where it fails,
> > rather than "knowing" ahead of time that it won't fit.
> > 
>
> Don't think so, since the media I've burnt were 10G and 22G large.

What growisofs definitely causes with formatting the media is to make it slow.

Growisofs is not a cleanly writen application. It frequently returns slightly 
modified mode data to the drive that was fetched before from the drive. The way 
this new data is created is in conflict with the SCSI standard. Some drives 
still accept the data others do not. In some cases, sending back identical data
will even switch the drive into unwanted behavior. A quick statement could be:
It was written in C++ but looks like assembly code.... Note that there was no 
update since 5 years and several people reported less problems when using 
cdrecord instead of growisofs.

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily


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

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=51da99c0.76yYmzUYur0m8Fl0%Joerg.Schilling@fokus.fraunhofer.de \
    --to=joerg.schilling@fokus.fraunhofer.de \
    --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