From: Admin <kernel@cideweb.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ittle problems with /dev/sr0 with 2.4.19-rc1
Date: Sun, 7 Jul 2002 14:58:01 +0200 [thread overview]
Message-ID: <200207071458.01519.kernel@cideweb.com> (raw)
In-Reply-To: <20020707101347.GA21065@codepoet.org>
On Domingo 07 Julio 2002 12:13, Erik Andersen wrote:
> 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
Hi, I get same error with /dev/hdc, when I try the same on /dev/sr0, box
freeze, kernel 2.4.17-xfs
Jul 7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331600
Jul 7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331604
Jul 7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331608
Jul 7 14:29:24 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:24 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:24 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331612
Jul 7 14:29:28 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:28 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:28 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331616
Jul 7 14:29:31 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:31 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:31 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331620
Jul 7 14:29:31 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:31 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:31 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331624
Jul 7 14:29:31 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:31 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:31 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331628
Jul 7 14:29:32 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:32 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:32 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331632
Jul 7 14:29:32 iceberg kernel: hdc: command error: status=0x51 { DriveReady
SeekComplete Error }
Jul 7 14:29:32 iceberg kernel: hdc: command error: error=0x50
Jul 7 14:29:32 iceberg kernel: end_request: I/O error, dev 16:00 (hdc),
sector 1331636
next prev parent reply other threads:[~2002-07-07 12:55 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
2002-07-07 12:58 ` Admin [this message]
-- 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=200207071458.01519.kernel@cideweb.com \
--to=kernel@cideweb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.