From: "J Pälve" <xtc@pcuf.fi>
To: xfs@oss.sgi.com
Subject: Write barriers and hardware RAID
Date: Fri, 17 Jul 2009 13:35:52 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.1.10.0907171259590.8586@pcuf.fi> (raw)
Hi,
I'm setting up a server to provide storage for a couple of VMware ESXi
servers. I'm using the latest stable Debian and I'm leaning towards using
NFS with XFS. However, I'm concerned about data integrity in the event of
power-out (we have UPS but they only last so long). Here are the specific
questions I have:
- The XFS FAQ states that with battery backup'd RAID hardware, both write
barriers and individual disk cache should be turned off. However, I'm
getting better benchmark results with both turned on. What I'm wondering
is, will write barriers work as intended when used with hardware RAID
controller (PERC 6/E)? Googling only turned up results relating to
software RAID.
- The XFS FAQ also states that virtualization products prevent write
barriers from working correctly. Is this still the case (specifically with
ESXi 3.5 and later) and is there anything that can be done about it? Does
VMFS somehow work around this, or is the problem then just "out of sight,
out of mind"?
Bregs,
JPa
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-07-17 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 10:35 J Pälve [this message]
2009-07-20 11:01 ` Write barriers and hardware RAID Michael Monnerie
[not found] <mailman.323.1248105112.225101.xfs@oss.sgi.com>
[not found] ` <alpine.LRH.1.10.0907210918150.14559@pcuf.fi>
2009-07-21 8:12 ` Michael Monnerie
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=alpine.LRH.1.10.0907171259590.8586@pcuf.fi \
--to=xtc@pcuf.fi \
--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