From: "Barry K. Nathan" <barryn@pobox.com>
To: Moritz Muehlenhoff <jmm@informatik.uni-bremen.de>
Cc: linux-kernel@vger.kernel.org, "Barry K. Nathan" <barryn@pobox.com>
Subject: Re: [BUG] 100% reproducible oops on ATAPI CD-ROM I/O error, 2.5.75
Date: Sun, 13 Jul 2003 19:18:36 -0700 [thread overview]
Message-ID: <20030714021836.GA25869@ip68-4-255-84.oc.oc.cox.net> (raw)
In-Reply-To: <E19bp2m-0006gf-00@regenbogen.informatik.uni-bremen.de>
On Mon, Jul 14, 2003 at 12:10:08AM +0200, Moritz Muehlenhoff wrote:
> Does anyone have an explanation why cdrecord fails to write the last
> sector properly? Is this a kernel issue or a bug in cdrecord?
> I'm using cdrtools 2.01a15.
If you don't specify "-dao" or an equivalent function to cdrecord, it
records in TAO mode by default. IIRC that mode *by definition* will
leave you with an extraneous unreadable sector (or maybe it's several, I
don't remember) after the actual data has ended. (Similarly, TAO gives
you 2 seconds of forced silence between audio tracks.)
So if you believe it's a bug, then you would have to argue that the bug
is in cdrecord's default choice of recording mode. However, if cdrecord
is changed to not do this by default, it could break compatibility with
some older recorders.
The other possible bug is in readcd. (I think) it should be able to
avoid choking on the extraneous sector(s) that result from recording the
CD in TAO mode. If you're running a reasonably recent 2.4 or 2.5 kernel
then dd handles this properly on most drives, however.
-Barry K. Nathan <barryn@pobox.com>
prev parent reply other threads:[~2003-07-14 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 9:33 [BUG] 100% reproducible oops on ATAPI CD-ROM I/O error, 2.5.75 Barry K. Nathan
2003-07-13 22:10 ` Moritz Muehlenhoff
2003-07-14 2:18 ` Barry K. Nathan [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=20030714021836.GA25869@ip68-4-255-84.oc.oc.cox.net \
--to=barryn@pobox.com \
--cc=jmm@informatik.uni-bremen.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).