From: Wakko Warner <wakko@animx.eu.org>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: Rick Warner <rick@microway.com>, linux-scsi@vger.kernel.org
Subject: Re: errors from mptsas
Date: Wed, 9 Apr 2008 12:32:08 -0400 [thread overview]
Message-ID: <20080409163208.GC12283@animx.eu.org> (raw)
In-Reply-To: <0631C836DBF79F42B5A60C8C8D4E8229FBDC71@NAMAIL2.ad.lsil.com>
Moore, Eric wrote:
> On Wednesday, April 09, 2008 4:54 AM, Rick Warner wrote:
> >
> > Join the club. I have an LSI SAS with 3x 750gb seagate sata drives in
> > raid5. Does this happen only on your SATA drives or all the drives?
> > Depending on the activity, it would drop one of them out of the
> > array. I think the problem has been solved for now by changing the
> > queue_depth to 1.
> >
> > echo 1 > /sys/block/sdX/device/queue_depth
> >
> > Here's the drives in my system:
> > [0:0:0:0] disk ATA ST3750640AS E /dev/sda
> > [0:0:1:0] disk ATA ST3750640AS E /dev/sdb
> > [0:0:2:0] disk ATA ST3750640AS E /dev/sdc
> >
>
>
> Rick - I thought you said the magic number was 32 for SATA devices? And
> we confirmed that in the logs you sent yesterday. Is that correct, or
> did I miss something.
That was ment for me.
>From what I read, the number is 31 for sata drives (I'm not sure about sas
and not sure if it relates to sata drives on a sas controller).
However, I set mine to 1 specifically and have not had a problem. I'd
rather not try 31 and a drive drop out again. It takes 4 hours to rebuild
the array and I've had to do it with the system offline.
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2008-04-09 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 22:20 errors from mptsas Rick Warner
2008-04-09 10:53 ` Wakko Warner
2008-04-09 15:11 ` Moore, Eric
2008-04-09 16:32 ` Wakko Warner [this message]
2008-04-09 15:16 ` Rick Warner
2008-04-09 16:30 ` Wakko Warner
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=20080409163208.GC12283@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=Eric.Moore@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rick@microway.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox