From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 13499] Write cache: disabled, read cache: enabled, supports DPO and FUA? it's bug???
Date: Wed, 10 Jun 2009 14:14:14 GMT [thread overview]
Message-ID: <200906101414.n5AEEEEZ004285@demeter.kernel.org> (raw)
In-Reply-To: <bug-13499-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13499
--- Comment #2 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2009-06-10 14:14:13 ---
Reply-To: James.Bottomley@HansenPartnership.com
On Wed, 2009-06-10 at 14:00 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> why Write cache: disabled??
The SCSI mid layer is merely reporting what your array is telling it.
For arrays without a battery backed cache, write through configuration
(i.e. read cache enabled, write cache disabled) is the usual safe
default.
You can alter your write cache settings using Doug Gilbert's
sg3-utils ... but be warned, enabling the write cache without battery
backing in an array is a dangerous thing to do since most arrays have
huge caches, they either ignore SYNCHRONIZE CACHE (which would leave you
vulnerable to data loss on power failure) or take such a long time, it
would kill performance.
James
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-06-10 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 13:59 [Bug 13499] New: Write cache: disabled, read cache: enabled, supports DPO and FUA? it's bug??? bugzilla-daemon
2009-06-10 14:00 ` [Bug 13499] " bugzilla-daemon
2009-06-10 14:14 ` James Bottomley
2009-06-10 14:14 ` bugzilla-daemon [this message]
2009-06-10 17:04 ` bugzilla-daemon
[not found] <bug-13499-11613@https.bugzilla.kernel.org/>
2012-06-08 11:47 ` bugzilla-daemon
2012-06-08 11:47 ` bugzilla-daemon
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=200906101414.n5AEEEEZ004285@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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