public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "bm" <b.melnicki@nova-trading.com>
To: "Alan Cox" <alan@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Further aacraid work
Date: Wed, 30 Jun 2004 04:02:53 +0200	[thread overview]
Message-ID: <008e01c45e46$5ad47050$0264a8c0@rck> (raw)
In-Reply-To: 20040616210455.GA13385@devserv.devel.redhat.com


Setup:
Tyan Thunder K8S Pro S2882, 2xAMD Opteron 248, 4GB RAM
Adaptec 2200S
5xFUJITSU MAS3184NC RAID0
(I've disconnected second enclosure to speed-up reboots)

Currently it boots from another disk via Tekram  390U2W so I have full
control
of aacraid module.

applied patches:
cset-alan@redhat.com_ChangeSet_20040618145535_60089.txt
cset-janitor@sternwelten.at_ChangeSet_20040622163213_10244.txt
cset-jejb@mulgrave.(none)_ChangeSet_20040622162621_09621.txt
cset-jejb@mulgrave.(none)_ChangeSet_20040622163045_09435.txt
cset-markh@osdl.org_ChangeSet_20040621214511_06962.txt

on increased file activity I'm getting this:

Jun 30 04:08:15 crusher Bootdata ok (command line is root=/dev/sda1 vga=788)
Jun 30 04:08:15 crusher Linux version 2.6.7-gentoo-r6 (root@crusher) (gcc
version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)) #1
SMP Mon Jun 28 09:52:04 CEST 2004
<snip>
Jun 30 04:08:35 crusher Red Hat/Adaptec aacraid driver (1.1.2-lk2 Jun 30
2004)
Jun 30 04:08:36 crusher AAC0: kernel 4.1.4 build 7244
Jun 30 04:08:36 crusher AAC0: monitor 4.1.4 build 7244
Jun 30 04:08:36 crusher AAC0: bios 4.1.0 build 7244
Jun 30 04:08:36 crusher AAC0: serial b74e68fafaf001
Jun 30 04:08:36 crusher AAC0: 64bit support enabled.
Jun 30 04:08:36 crusher AAC0: 64 Bit PAE enabled
Jun 30 04:08:36 crusher scsi1 : aacraid
Jun 30 04:08:36 crusher Vendor: ADAPTEC   Model: Adaptec Stripe    Rev: V1.0
Jun 30 04:08:36 crusher Type:   Direct-Access                      ANSI SCSI
revision: 02
Jun 30 04:08:36 crusher SCSI device sdc: 178699520 512-byte hdwr sectors
(91494 MB)
Jun 30 04:08:36 crusher sdc: Write Protect is off
Jun 30 04:08:36 crusher sdc: Mode Sense: 03 00 00 00
Jun 30 04:08:36 crusher SCSI device sdc: drive cache: write through
Jun 30 04:08:36 crusher /dev/scsi/host1/bus0/target0/lun0: p1
Jun 30 04:08:36 crusher Attached scsi removable disk sdc at scsi1, channel
0, id 0, lun 0
Jun 30 04:08:36 crusher Attached scsi generic sg2 at scsi1, channel 0, id 0,
lun 0,  type 0
Jun 30 04:09:59 crusher kjournald starting.  Commit interval 5 seconds
Jun 30 04:09:59 crusher EXT3 FS on sdc1, internal journal
Jun 30 04:09:59 crusher EXT3-fs: recovery complete.
Jun 30 04:09:59 crusher EXT3-fs: mounted filesystem with ordered data mode.
Jun 30 04:11:13 crusher write_callback: write failed, status = 5
Jun 30 04:11:13 crusher SCSI error : <1 0 0 0> return code = 0x8000002
Jun 30 04:11:13 crusher Info fld=0x0, Current sdc: sense key Hardware Error
Jun 30 04:11:13 crusher Additional sense: Internal target failure
Jun 30 04:11:13 crusher end_request: I/O error, dev sdc, sector 47395279
Jun 30 04:11:13 crusher Buffer I/O error on device sdc1, logical block
5924402
Jun 30 04:11:13 crusher lost page write due to I/O error on sdc1
Jun 30 04:11:14 crusher write_callback: write failed, status = 5
Jun 30 04:11:14 crusher SCSI error : <1 0 0 0> return code = 0x8000002
Jun 30 04:11:14 crusher Info fld=0x0, Current sdc: sense key Hardware Error
Jun 30 04:11:14 crusher Additional sense: Internal target failure
Jun 30 04:11:14 crusher end_request: I/O error, dev sdc, sector 47393319
Jun 30 04:11:14 crusher Buffer I/O error on device sdc1, logical block
5924157
Jun 30 04:11:14 crusher lost page write due to I/O error on sdc1
Jun 30 04:11:14 crusher write_callback: write failed, status = 5
Jun 30 04:11:14 crusher SCSI error : <1 0 0 0> return code = 0x8000002
Jun 30 04:11:14 crusher Info fld=0x0, Current sdc: sense key Hardware Error
Jun 30 04:11:14 crusher Additional sense: Internal target failure
Jun 30 04:11:14 crusher end_request: I/O error, dev sdc, sector 47397239
Jun 30 04:11:14 crusher Buffer I/O error on device sdc1, logical block
5924647
Jun 30 04:11:14 crusher lost page write due to I/O error on sdc1
Jun 30 04:11:14 crusher write_callback: write failed, status = 5
Jun 30 04:11:14 crusher SCSI error : <1 0 0 0> return code = 0x8000002
Jun 30 04:11:14 crusher Info fld=0x0, Current sdc: sense key Hardware Error
Jun 30 04:11:14 crusher Additional sense: Internal target failure
Jun 30 04:11:14 crusher end_request: I/O error, dev sdc, sector 47390183
Jun 30 04:11:14 crusher Buffer I/O error on device sdc1, logical block
5923765
Jun 30 04:11:14 crusher lost page write due to I/O error on sdc1
Jun 30 04:11:43 crusher aacraid: Host adapter reset request. SCSI hang ?
Jun 30 04:11:44 crusher aacraid: Host adapter appears dead
Jun 30 04:11:44 crusher scsi: Device offlined - not ready after error
recovery: host 1 channel 0 id 0 lun 0
Jun 30 04:11:44 crusher scsi: Device offlined - not ready after error
recovery: host 1 channel 0 id 0 lun 0

<snip>
Jun 30 04:11:45 crusher scsi: Device offlined - not ready after error
recovery: host 1 channel 0 id 0 lun 0
Jun 30 04:11:45 crusher scsi: Device offlined - not ready after error
recovery: host 1 channel 0 id 0 lun 0
Jun 30 04:11:45 crusher SCSI error : <1 0 0 0> return code = 0x6000000
Jun 30 04:11:45 crusher end_request: I/O error, dev sdc, sector 47389407
Jun 30 04:11:45 crusher Buffer I/O error on device sdc1, logical block
5923668
Jun 30 04:11:45 crusher lost page write due to I/O error on sdc1
Jun 30 04:11:45 crusher scsi1 (0:0): rejecting I/O to offline device
Jun 30 04:11:45 crusher Buffer I/O error on device sdc1, logical block
5923669
Jun 30 04:11:45 crusher lost page write due to I/O error on sdc1
Jun 30 04:11:45 crusher Buffer I/O error on device sdc1, logical block
5923670
Jun 30 04:11:45 crusher lost page write due to I/O error on sdc1


What can I do ? I'm so desperate that I'm thinking switching to another
RAID controller. BTW which one of dual-channel U320 with cache have stable
drivers for x86_64 platform ?

regards,
Bartholomew Melnicki




  parent reply	other threads:[~2004-06-30  2:01 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 21:04 PATCH: Further aacraid work Alan Cox
2004-06-16 21:33 ` Christoph Hellwig
2004-06-16 21:40   ` Alan Cox
2004-06-16 21:42     ` Christoph Hellwig
2004-06-16 21:48       ` Alan Cox
2004-06-16 21:58         ` Christoph Hellwig
2004-06-16 22:06           ` Alan Cox
2004-06-29 17:48 ` Byron Stanoszek
2004-06-29 18:27   ` Mark Haverkamp
2004-06-29 18:37   ` Alan Cox
2004-06-30  2:02 ` bm [this message]
2004-06-30 16:07   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17 12:53 Salyzyn, Mark
2004-06-17 13:07 ` Matthew Wilcox
2004-06-17 13:19   ` Christoph Hellwig
2004-06-17 13:55   ` James Bottomley
2004-06-17 13:32 ` Christoph Hellwig
2004-06-17 14:02 ` Alan Cox
2004-06-17 14:39 Salyzyn, Mark
2004-06-17 14:55 ` James Bottomley
2004-06-17 14:58   ` Alan Cox
2004-06-17 15:15     ` Arjan van de Ven
2004-06-17 19:16       ` James Bottomley
2004-06-17 16:32   ` Clay Haapala
2004-06-17 16:37     ` James Bottomley
2004-06-17 16:46     ` Alan Cox
2004-06-17 15:11 ` Anton Blanchard
2004-06-17 17:54 Salyzyn, Mark
2004-06-17 20:38 ` Alan Cox
2004-06-17 20:48   ` William Lee Irwin III
2004-06-17 20:56     ` James Bottomley
2004-06-18 15:05     ` William Lee Irwin III
2004-06-18 20:32       ` William Lee Irwin III
2004-06-27 17:33         ` James Bottomley
     [not found] <286GI-5y3-11@gated-at.bofh.it>
     [not found] ` <286Qp-5EU-19@gated-at.bofh.it>
2004-06-17 19:10   ` Andi Kleen
2004-06-17 20:54     ` Alan Cox
2004-06-17 21:13       ` James Bottomley
2004-06-17 21:25       ` Andi Kleen
2004-06-18 15:19         ` Benjamin Herrenschmidt
2004-06-18  5:57       ` Jeff Garzik
2004-06-18 14:07         ` James Bottomley
2004-06-18 15:17     ` Benjamin Herrenschmidt
2004-06-18 20:53 Salyzyn, Mark
2004-06-28 13:17 Salyzyn, Mark
2004-06-29 18:53 Salyzyn, Mark
2004-06-29 19:03 ` Byron Stanoszek
2004-06-29 19:27 Salyzyn, Mark
2004-06-29 20:20 ` Byron Stanoszek
2004-06-29 20:42 ` Alan Cox
2004-06-29 20:55 Salyzyn, Mark
2004-06-29 23:22 ` Byron Stanoszek
2004-06-30 19:52 ` Byron Stanoszek
2004-06-30 19:59   ` Dario

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='008e01c45e46$5ad47050$0264a8c0@rck' \
    --to=b.melnicki@nova-trading.com \
    --cc=alan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox