From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: XFS and write barriers.
Date: Thu, 29 Mar 2007 16:56:21 +0200 [thread overview]
Message-ID: <200703291656.22084.Martin@lichtvoll.de> (raw)
In-Reply-To: <20070326090456.GO32597093@melbourne.sgi.com>
Am Montag 26 März 2007 schrieb David Chinner:
> > Is there some mount flag to say "cope without barriers" or "require
> > barriers" ??
>
> XFs has "-o nobarrier" to say don't use barriers, and this is
> *not* the default. If barriers don't work, we drop back to "-o
> nobarrier" after leaving a loud warning inthe log....
Hello David!
Just a thought, maybe it shouldn't do that automatically, but require the
sysadmin to explicitely state "-o nobarrier" in that case. Safest default
behavior IMHO would be either not to mount at all without "-o nobarrier"
if the device has no barrier support or disable the write cache of that
device. The latter can be considered a layering violation in itself.
BTW XFS copes really well here with commodity hardware such as my
ThinkPads with 2.5 inch notebook harddisks *since* 2.6.17.7.
But right now I wondered about barrier support on USB connected devices? I
have to check whether XFS does barriers on those. Does the usb mass
storage driver support barriers?
Regards,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2007-03-29 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 1:26 XFS and write barriers Neil Brown
2007-03-23 5:30 ` David Chinner
2007-03-23 7:49 ` Neil Brown
2007-03-25 4:17 ` David Chinner
2007-03-25 23:21 ` Neil Brown
2007-03-26 3:14 ` David Chinner
2007-03-26 4:27 ` Neil Brown
2007-03-26 9:04 ` David Chinner
2007-03-29 14:56 ` Martin Steigerwald [this message]
2007-03-29 15:18 ` David Chinner
2007-03-29 16:49 ` Martin Steigerwald
2007-03-23 9:50 ` Christoph Hellwig
2007-03-25 3:51 ` David Chinner
2007-03-25 23:58 ` Neil Brown
2007-03-26 1:11 ` Neil Brown
2007-03-23 6:20 ` Timothy Shimmin
2007-03-23 8:00 ` Neil Brown
2007-03-25 3:19 ` David Chinner
2007-03-26 0:01 ` Neil Brown
2007-03-26 3:58 ` David Chinner
2007-03-27 3:58 ` Timothy Shimmin
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=200703291656.22084.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-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