From: Eric Sandeen <sandeen@sandeen.net>
To: Adam Fried-Gintis <xfs@icosm.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS without write barriers - safe on multipath device?
Date: Fri, 16 Jan 2009 16:31:00 -0600 [thread overview]
Message-ID: <49710AA4.3000402@sandeen.net> (raw)
In-Reply-To: <8998fba30901161409m37058e10yc25e062fad425710@mail.gmail.com>
Adam Fried-Gintis wrote:
> Hi,
> I am just curious, if I see the warning that write barrier support is
> disabled when mounting an XFS filesystem through md multipath, does XFS have
> some OTHER provision for protecting the order of its writes to the
> underlying device, or is it unsafe to run with write back caching at that
> point? My underlying device is an active/active storage system - combined
> with the multipath driver, we are seeing metadata corruption on the
> filesystem, and I'm just trying to figure out if this is an invalid
> configuration to test or if the storage device is doing something wrong.
XFS needs to know that when the storage says a write is complete, that
it really is safe on disk.
You're ok w/o barriers if either:
a) you have no write cache, or
b) you know your write cache is guaranteed to hit the disks (UPS?)
Also, this only comes into play when the drives lose power and lose
their write cache. If that's not happening to you, then your problem is
likely not related to barrier issues.
When you say active/active; do you have 2 hosts directly accessing the
same filesystem on a SAN?
-Eric
> Thanks!
>
> ---
> Adam Fried-Gintis
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-01-16 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:09 XFS without write barriers - safe on multipath device? Adam Fried-Gintis
2009-01-16 22:31 ` Eric Sandeen [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=49710AA4.3000402@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@icosm.net \
--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