From: "David Dabbs" <david@dabbs.net>
To: 'ReiserFS List' <reiserfs-list@namesys.com>
Subject: RE: yeah, it was hardware error, we can ship!
Date: Thu, 5 Aug 2004 10:29:07 -0500 [thread overview]
Message-ID: <20040805153225.D2E5B15D2F@mail03.powweb.com> (raw)
In-Reply-To: <16654.53838.10331.358355@gargle.gargle.HOWL>
> -----Original Message-----
> From: Nikita Danilov [mailto:nikita@clusterfs.com]
> Sent: Monday, August 02, 2004 6:46 PM
> To: Hans Reiser
> Cc: David Dabbs; 'ReiserFS List'
> Subject: Re: yeah, it was hardware error, we can ship!
>
> Hans Reiser writes:
> > Nikita Danilov wrote:
> > >
> > Are your words intended to suggest that it is not a hardware bug, and
> > thus might be software?
>
> Yes, these messages are harmless. I am getting them also, on a brand-new
> disk, SuSE9.1
>
> Jul 3 10:44:04 tau kernel: hda: drive_cmd: status=0x51 { DriveReady
> SeekComplete Error }
> Jul 3 10:44:04 tau kernel: hda: drive_cmd: error=0x04 { DriveStatusError
> }
> Jul 3 10:44:04 tau kernel: hda: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Jul 3 10:44:04 tau kernel: hda: task_no_data_intr: error=0x04 {
> DriveStatusError }
>
> Search for SeekComplete in the LKML archive.
>
> Nikita.
Well, whether or not the messages are innocuous, they are gone. I have a new
refurbished disk that provides more space and is faster. And I am rerunning
the mongo benchmarks whose failure started this thread.
David
prev parent reply other threads:[~2004-08-05 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 18:30 yeah, it was hardware error, we can ship! Hans Reiser
2004-08-04 18:40 ` David Dabbs
2004-08-04 18:56 ` Lamont R. Peterson
2004-08-04 19:13 ` David Dabbs
2004-08-04 20:48 ` Nikita Danilov
2004-08-04 21:36 ` Hans Reiser
2004-08-02 23:46 ` Nikita Danilov
2004-08-05 15:29 ` David Dabbs [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=20040805153225.D2E5B15D2F@mail03.powweb.com \
--to=david@dabbs.net \
--cc=reiserfs-list@namesys.com \
/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.