From: Emmanuel Florac <eflorac@intellique.com>
To: "Georg Schönberger" <g.schoenberger@xortex.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS and nobarrier with SSDs
Date: Mon, 14 Dec 2015 12:48:54 +0100 [thread overview]
Message-ID: <20151214124854.51fad2d1@harpe.intellique.com> (raw)
In-Reply-To: <E127700EFE58FD45BD6298EAC813FA42020D8173@TIGER2010.xortex.local>
Le Sat, 12 Dec 2015 10:24:25 +0000
Georg Schönberger <g.schoenberger@xortex.com> écrivait:
> I have found a recent discussion on the Ceph mailing list, anyone
> from XFS that can help us?
>
See this article from someone using many SSDs:
http://blog.nordeus.com/dev-ops/power-failure-testing-with-ssds.htm
If you want to know if a particular SSD model is reliable, your best
option is to buy one, write a lot of data to it, and pull the plug on
the machine repeatedly while it's writing, and see what's happening
when using barriers or not.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-12-14 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 10:24 XFS and nobarrier with SSDs Georg Schönberger
2015-12-12 12:26 ` Martin Steigerwald
2015-12-14 6:43 ` Georg Schönberger
2015-12-14 8:38 ` Martin Steigerwald
2015-12-14 9:58 ` Christoph Hellwig
2015-12-14 10:18 ` Georg Schönberger
2015-12-14 10:27 ` Christoph Hellwig
2015-12-14 10:34 ` Georg Schönberger
2015-12-14 16:39 ` Eric Sandeen
2015-12-26 23:44 ` Linda Walsh
2015-12-14 11:48 ` Emmanuel Florac [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=20151214124854.51fad2d1@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=g.schoenberger@xortex.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