public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas Berry" <nikberry@med.umich.edu>
To: <pochini@denise.shiny.it>, <linux-kernel@vger.kernel.org>
Subject: Re: aic7xxx and error recovery
Date: Fri, 01 Nov 2002 12:00:36 -0500	[thread overview]
Message-ID: <sdc26cf0.091@mail-02.med.umich.edu> (raw)

At the time I read  your original post, I was investigating why one drive kept being kicked out of an md array.

This is on two systems, 2.4.20-pre11 and 2.4.20-rc1, and both using a symc53c875 with 36gb IBM drives.

Turns out it's recovered errors, just like you see.

So it seems to be wider than aic7xxx. I've just rebuilt both arrays with PER 0, and they're working fine.

Another array on 2.4.19-pre7 & aic7xxx works fine with PER 1

Nik


>>> Giuliano Pochini <pochini@denise.shiny.it> 11/01/02 03:16AM >>>
Giuliano Pochini wrote:
>
> [...] It happens that when a recoverable error occurs (as
> reported in the sys logs) read()(2) returns a value smaller then
> requested, and the loaded data is identical to the pattern, or
> read() completes, but the data is wrong.

Ehm, I made a stupid typo in my test program. read() does dot
succeed in the second case. Anyway the problem is still here:
why does it fail on recovered errors ?


Bye.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org 
More majordomo info at  http://vger.kernel.org/majordomo-info.html 
Please read the FAQ at  http://www.tux.org/lkml/


             reply	other threads:[~2002-11-01 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 17:00 Nicholas Berry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:35 aic7xxx and error recovery Giuliano Pochini
2002-11-01  8:16 ` Giuliano Pochini

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=sdc26cf0.091@mail-02.med.umich.edu \
    --to=nikberry@med.umich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@denise.shiny.it \
    /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