From: Eric Sandeen <sandeen@sandeen.net>
To: David Lethe <david@santools.com>
Cc: Timothy Shimmin <tes@sgi.com>, xfs-oss <xfs@oss.sgi.com>,
LinuxRaid <linux-raid@vger.kernel.org>, NeilBrown <neilb@suse.de>,
jeremy@sgi.comwe
Subject: Re: [PATCH] disable queue flag test in barrier check
Date: Thu, 26 Jun 2008 09:57:18 -0500 [thread overview]
Message-ID: <4863AE4E.5060908@sandeen.net> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97CDBCF11@34093-C3-EVS3.exchange.rackspace.com>
David Lethe wrote:
> Fyi - related problem is seen with solaris & zfs when users attach them
> to hardware-based RAID subsystems. The vendors had
> to make firmware tweaks to address solaris's
> flush-to-disk-after-all-writes.
>
> Not sure what you mean about non-volatile vs. volatile write cache,
> however. If you want to see if write cache is enabled on a disk drive,
> or
> Even a logical disk on a hardware-based RAId, under Linux, then google
> "mode page editor" for lots of choices. Also look up zfs write cache
> raid and you'll get information that you can just as easily apply to
> Linux implementations of md.
I'm not so interested in whether it is enabled; I'd like to know if it
is safe (to varying degrees) in the event of a power failure, and I
don't think there's any way we can know that.
So the administrator, if she's sure that all cached writes will hit disk
even if a breaker pops, can disable barriers. If it's just a 32MB cache
seagate drive plugged into the wall, you probably had better be sure
barriers are enabled or you may well have a scrambled filesystem
post-power-outage.
-Eric
next prev parent reply other threads:[~2008-06-26 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 3:07 [PATCH] disable queue flag test in barrier check Eric Sandeen
2008-06-26 8:25 ` Timothy Shimmin
2008-06-26 13:25 ` Eric Sandeen
2008-06-26 14:47 ` David Lethe
2008-06-26 14:57 ` Eric Sandeen [this message]
2008-06-27 4:51 ` Timothy Shimmin
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 15:24 David Lethe
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=4863AE4E.5060908@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@santools.com \
--cc=jeremy@sgi.comwe \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tes@sgi.com \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).