linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: bloch@verdurin.com
Cc: linux-scsi@vger.kernel.org, linux-precision@dell.com
Subject: Re: Very slow writes with mptsas
Date: Wed, 20 Jun 2007 13:30:39 -0400	[thread overview]
Message-ID: <4679643F.3010309@torque.net> (raw)
In-Reply-To: <20070612141511.GB4347@bloch.config>

bloch@verdurin.com wrote:
> On Tue, 05 Jun 2007, bloch@verdurin.com wrote:
> 
>> Hello
>>
>> I'm seeing very slow writes on a Dell Precision 690 with the Dell SAS5
>> adapter, serving a RAID1 array of SATA-II disks.
>>
>> It's very similar to the problem in FreeBSD, described here:
>>
>> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-03/msg00756.html
>>
>> I'm running FC6 with the latest kernel.
>>
>> Reads are quite fast, writes terribly slow.
>>
> 
> Thanks to all who replied to this query, especially the very detailed
> response from Eric Moore at LSI.
> 
> The first important facet is that we need to operate on the two hidden
> physical disks, not the RAID device.  lsscsi differentiates them:
> 
> # lsscsi
> [0:0:0:0]    disk    ATA      WDC WD5000KS-75M 2E08  -       
> [0:0:1:0]    disk    ATA      HDS725050KLA360  AB5A  -       
> [0:1:0:0]    disk    Dell     VIRTUAL DISK     1028  /dev/sda
> 
> sg_map gives the generic device numbers:

Using 'lsscsi -g' would also give you the generic device
numbers.

It is interesting that the above "ATA" disks do not have
corresponding /dev/sd* device names.

> # sg_map -i -x
> /dev/sg0  0 0 0 0  0  ATA       WDC WD5000KS-75M  2E08
> /dev/sg1  0 0 1 0  0  ATA       HDS725050KLA360   AB5A
> 
> The write cache can then be enabled using sdparm:
> 
> sdparm -s WCE=1 -S /dev/sg0
> 
> and the result checked with
> 
> # sdparm -g WCE /dev/sg1
> /dev/sg1: ATA       HDS725050KLA360   AB5A
> WCE         1  [cha: y]
> 
> This seems to make the write performance much better.

Good.

> The question for Dell is why their version of the BIOS doesn't set the
> write cache in the first place or allow it to be altered by the user.

The mechanism for doing this was only formalized recently
with the SAT standard, so it may take a while for BIOSes
and other infrastructure to catch up.

Doug Gilbert



      reply	other threads:[~2007-06-20 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 16:16 Very slow writes with mptsas bloch
2007-06-06  5:32 ` Matthew Jacob
2007-06-06 18:06   ` Douglas Gilbert
2007-06-07 21:42     ` bloch
2007-06-07 22:23     ` Moore, Eric
2007-06-12 14:15 ` bloch
2007-06-20 17:30   ` Douglas Gilbert [this message]

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=4679643F.3010309@torque.net \
    --to=dougg@torque.net \
    --cc=bloch@verdurin.com \
    --cc=linux-precision@dell.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;
as well as URLs for NNTP newsgroup(s).