From: Eric Sandeen <sandeen@sandeen.net>
To: Richard Bade <hitrich@gmail.com>, xfs@oss.sgi.com
Subject: Re: XFS and nobarriers on Intel SSD
Date: Thu, 3 Sep 2015 08:33:52 -0500 [thread overview]
Message-ID: <55E84C40.8020602@sandeen.net> (raw)
In-Reply-To: <CA+nZN+grRZBNruxua4inJ-cMe_WX2XSPjsrP+qb579Si8R6ihA@mail.gmail.com>
On 9/2/15 9:24 PM, Richard Bade wrote:
> Hi Everyone, I have a question about nobarriers. In the XFS FAQ it
> looks like the recommendation is that if you have a Battery Backed
> raid controller you should set nobarriers for performance reasons.
> Our LSI card doesn’t have battery backed cache as it’s configured in
> HBA mode (IT) rather than Raid (IR). Our Intel s3710 SSD’s do have a
> capacitor backed cache though. So is it recommended that barriers are
> turned off as the drive has a safe cache (I am confident that the
> cache will write out to disk on power failure)?
If you have a device which guarantees that every acknowledged write
will persist even if power is lost, then you can safely turn off
barriers.
> The reason I am asking about this is that we are seeing some
> significant I/O delays on the disks causing a “SCSI Task Abort” from
> the OS. This seems to be triggered by the drive receiving a
> “Synchronize cache command”. My current thinking is that setting no
> barriers will stop the drive receiving a sync command and therefore
> stop the I/O delay associated with it.
Interesting, I thought that usually devices with battery-backed cache
will just ignore synchronize cache commands.
But if not, then sure, maybe that's the issue.
-Eric
> This is happening on our Ceph storage cluster. For those not familiar
> with Ceph, it uses XFS as the underlying filesystem for the object
> stores.
>
> Has anyone else encountered this issue? Any info or suggestions about
> this would be appreciated.
>
> Regards, Richard
>
>
>
> _______________________________________________ xfs mailing list
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-03 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 2:24 XFS and nobarriers on Intel SSD Richard Bade
2015-09-03 13:33 ` Eric Sandeen [this message]
2015-09-03 13:43 ` Eric Sandeen
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=55E84C40.8020602@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hitrich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.