linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: IDE CDROM tail read errors
Date: Sun, 02 Apr 2006 12:55:23 +0200	[thread overview]
Message-ID: <m3hd5ctffo.fsf@defiant.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0603301016290.30783@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Thu, 30 Mar 2006 10:19:48 +0200 (MEST)")

Jan Engelhardt <jengelh@linux01.gwdg.de> writes:

>>first: 1 last 1
>>track:   1 lba:         0 (        0) 00:02:00 adr: 1 control: 4 mode: 1
>>track:lout lba:    335566 (  1342264) 74:36:16 adr: 1 control: 4 mode: -1
>>
>>FC-5-i386-disc1.iso size = 335564 * 2048 bytes, not sure why TOC has
>>2 more sectors (8 512B sectors) but I'm not a CD expert.
>>
>
> I have heard from friends that this is due to how readahead works. It 
> reads beyond the end of the track, and logically, the hardware signals an 
> error (leading to missing bytes at the end). It is said to be solved using 
> the -pad option when writing CDs.

You mean the read error and not TOC <> .iso track length differences?
-- 
Krzysztof Halasa

  reply	other threads:[~2006-04-02 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 19:11 IDE CDROM tail read errors Krzysztof Halasa
2006-03-30  8:19 ` Jan Engelhardt
2006-04-02 10:55   ` Krzysztof Halasa [this message]
2006-04-02 18:13     ` Jan Engelhardt
2006-03-30 11:18 ` Alan Cox
2006-04-02 10:50   ` Krzysztof Halasa
2006-04-04 19:09   ` Bill Davidsen
2006-04-12  8:57     ` Alan Cox

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=m3hd5ctffo.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-ide@vger.kernel.org \
    --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).