public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Raoul Bhatia [IPAX]" <r.bhatia@ipax.at>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic94xx driver woes continued
Date: Thu, 20 Mar 2008 20:15:59 +0100	[thread overview]
Message-ID: <47E2B7EF.1050203@ipax.at> (raw)
In-Reply-To: <1206039714.3038.40.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]

James Bottomley wrote:
> This is all normal.  Seagate drives are known for throwing protocol
> errors under stress at certain revs of firmware.  That's what
> REQ_TASK_ABORT, reason=0x6 is.
> 
> Your logs indicate that the recovery occurred correctly (as in all tasks
> were eventually retried), so it doesn't show an actual problem.

ok, i already filed a trouble ticket at seagate - lets see if they
provide a firmware update for the disks. afaik mine is "firmware 0002"

>> sometimes even a disk is kicked out of the raid configuration.
> 
> This would be abnormal, if you have a log of this, could you post it.  I
> assume it was because of I/O errors?

i attached a bigger syslog file (.gz format).

the errors look like:
> syslog.1.gz:Mar 11 06:25:08 db-ipax-164 kernel: raid1: Disk failure on sda1, disabling device. 
> syslog.1.gz:Mar 11 06:25:01 db-ipax-164 kernel: raid10: Disk failure on sda7, disabling device. 
> syslog.1.gz:Mar 10 18:13:25 db-ipax-164 kernel: raid10: Disk failure on sda3, disabling device. 
> syslog.1.gz:Mar 10 18:13:23 db-ipax-164 kernel: raid10: Disk failure on sda9, disabling device. 
> syslog.1.gz:Mar 10 18:13:23 db-ipax-164 kernel: raid10: Disk failure on sda8, disabling device. 
> syslog.1.gz:Mar 10 18:13:23 db-ipax-164 kernel: raid10: Disk failure on sda5, disabling device. 
> syslog.0:Mar 18 18:30:48 db-ipax-164 kernel: raid10: Disk failure on sdd5, disabling device. 
> syslog.0:Mar 18 18:27:18 db-ipax-164 kernel: raid10: Disk failure on sdd8, disabling device. 

i will test the device for itself to see if it has errors.

cheers,
raoul
-- 
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia@ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OEG         web.          http://www.ipax.at
Barawitzkagasse 10/2/2/11           email.            office@ipax.at
1190 Wien                           tel.               +43 1 3670030
FN 277995t HG Wien                  fax.            +43 1 3670030 15
____________________________________________________________________


[-- Attachment #2: syslog.0.gz --]
[-- Type: application/x-gzip, Size: 257896 bytes --]

  parent reply	other threads:[~2008-03-20 19:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 18:43 aic94xx driver woes continued Raoul Bhatia [IPAX]
2008-03-20 19:01 ` James Bottomley
2008-03-20 19:14   ` Raoul Bhatia [IPAX]
2008-03-29 22:36     ` Luben Tuikov
2008-03-20 19:15   ` Raoul Bhatia [IPAX] [this message]
2008-03-20 19:18     ` Raoul Bhatia [IPAX]
2008-03-20 19:57     ` James Bottomley
2008-03-20 20:21       ` Raoul Bhatia [IPAX]
2008-03-20 21:08       ` Raoul Bhatia [IPAX]
2008-03-20 21:17         ` James Bottomley
2008-03-20 22:18           ` Alexis Bruemmer
2008-03-26 14:34             ` Raoul Bhatia [IPAX]
2008-03-29 22:39       ` Luben Tuikov
2008-03-29 22:33   ` Luben Tuikov
2008-03-31 20:23     ` Raoul Bhatia [IPAX]

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=47E2B7EF.1050203@ipax.at \
    --to=r.bhatia@ipax.at \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@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