From: Erik Andersen <andersen@codepoet.org>
To: Christian Robert <xtian-test@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ittle problems with /dev/sr0 with 2.4.19-rc1
Date: Sun, 7 Jul 2002 04:13:47 -0600 [thread overview]
Message-ID: <20020707101347.GA21065@codepoet.org> (raw)
In-Reply-To: <3D2812F0.C3A4441D@sympatico.ca>
On Sun Jul 07, 2002 at 06:07:44AM -0400, Christian Robert wrote:
> [root@X-home:/btemp] # md5sum /dev/sr0
> md5sum: /dev/sr0: Input/output error <- oups, it failed
>
> [root@X-home:/btemp] # dd if=/dev/sr0 | md5sum
> dd: reading `/dev/sr0': Input/output error <- failed here too
> 13440+0 records in
> 13440+0 records out
> 5ec08b6fa7bf09741d1310e5baa800de - <- but md5sum is OK
Looks like a read ahead bug to me... Out of curiousity,
did you use "-no-pad" with mkisofs?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-07-07 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 10:07 ittle problems with /dev/sr0 with 2.4.19-rc1 Christian Robert
2002-07-07 10:13 ` Erik Andersen [this message]
2002-07-07 12:58 ` Admin
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 12:33 Tony Spinillo
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=20020707101347.GA21065@codepoet.org \
--to=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xtian-test@sympatico.ca \
/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