From: Adrian von Bidder <avbidder@fortytwo.ch>
To: linux-scsi@vger.kernel.org
Subject: aacraid on Poweredge 2650 ()
Date: Wed, 19 Apr 2006 16:55:18 +0200 [thread overview]
Message-ID: <200604191655.43350.avbidder@fortytwo.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 2977 bytes --]
Yo!
Running a Dell Poweredge 2650, I run into a stability problem triggered by
lots of disk activity (sometimes just tarring the whole filesystem for
backup or creating a new chroot would suffice, sometimes hundreds of GB of
filetransfers were necessary)
This was with Debian stable (2.6.8 kernel), and with what appeared to be a
half-buggy disk and a (ecc-correctable) faulty memory. Now, with replaced
hardware and with the 2.6.15 kernel (aac 1.1-4), things seem to be better.
(replacing the hardware alone didn't help, so it seemed to be a driver
problem.)
A quick test, moving a few 100G and a few 1000 files, couldn't reproduce the
issue, but still: are there known stability problems with that driver
version? Is there a changelog of the aacraid driver somewhere?
thanks in advance
-- vbi
relevant kernel messages afaict:
===
Adaptec aacraid driver (1.1-4 Mar 7 2006 02:24:50)
AAC0: kernel 2.7-1[3170]
AAC0: monitor 2.7-1[3170]
AAC0: bios 2.7-1[3170]
AAC0: serial d15810d3
scsi0 : percraid
Vendor: DELL Model: 3 discs and HS Rev: V1.0
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 142183296 512-byte hdwr sectors (72798 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: got wrong page
sda: assuming drive cache: write through
SCSI device sda: 142183296 512-byte hdwr sectors (72798 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: got wrong page
sda: assuming drive cache: write through
sda: sda1 sda2 sda3 < sda5 sda6 >
sd 0:0:0:0: Attached scsi removable disk sda
===
lspci output
===
0000:04:08.1 RAID bus controller: Dell PowerEdge Expandable RAID Controller
3/Di (rev 01)
Subsystem: Dell: Unknown device 0121
Flags: bus master, 66MHz, slow devsel, latency 32, IRQ 185
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at fcb00000 [disabled] [size=64K]
Capabilities: [80] Power Management version 2
0000:05:06.0 SCSI storage controller: Adaptec RAID subsystem HBA (rev 01)
Subsystem: Dell PowerEdge 2400,2500,2550,4400
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 7
BIST result: 00
I/O ports at cc00 [size=256]
Memory at fccff000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at fcd00000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
0000:05:06.1 SCSI storage controller: Adaptec RAID subsystem HBA (rev 01)
Subsystem: Dell PowerEdge 2400,2500,2550,4400
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
BIST result: 00
I/O ports at c800 [size=256]
Memory at fccfe000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at f8100000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
===
--
Life is fraught with opportunities to keep your mouth shut.
[-- Attachment #2: Type: application/pgp-signature, Size: 388 bytes --]
next reply other threads:[~2006-04-19 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 14:55 Adrian von Bidder [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-19 18:25 aacraid on Poweredge 2650 () Salyzyn, Mark
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=200604191655.43350.avbidder@fortytwo.ch \
--to=avbidder@fortytwo.ch \
--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