All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Halim Issa <yallaone@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: sd incorrectly reports write cache disabled on cache-capable drives/controllers
Date: Fri, 25 Jan 2008 15:33:21 -0600	[thread overview]
Message-ID: <1201296801.3119.63.camel@localhost.localdomain> (raw)
In-Reply-To: <200801252228.22659.yallaone@gmail.com>


On Fri, 2008-01-25 at 22:28 +0100, Halim Issa wrote:
> Thank you so much for the quick reply - I risk asking one follow-up question.
> 
> On Friday 25 January 2008 22:15:20 James Bottomley wrote:
> > The "cache" hear would be referring to the RAID controller cache, not
> > the disk cache.  Likewise DPO and FUA refer to what the RAID controller
> > can support, not the disk.
> 
> Would it be safe to assume that the problem thus lies within the mptfusion 
> driver, since a) the LSI Logic controller in question does indeed have 
> hardware cache capabilities; and b) an older kernel version as well as 
> Windows Server, correctly loads with the correct cache parameters at boot?

I don't think it would be correct to assume that there actually is a
problem.  Most RAID controllers habitually lie about having a cache in
their INQUIRY strings because they don't want to deal with the kernel
sending SYNCHRONIZE_CACHE commands down.

Just because the inquiry strings say it doesn't have a cache doesn't
really mean it's not using one but not telling anyone.

James



  reply	other threads:[~2008-01-25 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 20:59 sd incorrectly reports write cache disabled on cache-capable drives/controllers Halim Issa
2008-01-25 21:15 ` James Bottomley
2008-01-25 21:28   ` Halim Issa
2008-01-25 21:33     ` James Bottomley [this message]
2008-01-25 21:52       ` Halim Issa
2008-01-31 10:41       ` Halim Issa

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=1201296801.3119.63.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=yallaone@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.