From: Marc MERLIN <marc@merlins.org>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Migrate to bcache: A few questions
Date: Mon, 30 Dec 2013 01:01:25 -0800 [thread overview]
Message-ID: <20131230090125.GN19863@merlins.org> (raw)
In-Reply-To: <fgu6pa-f1b.ln1@hurikhan77.spdns.de>
On Mon, Dec 30, 2013 at 02:22:55AM +0100, Kai Krakow wrote:
> These thought are actually quite interesting. So you are saying that data
> may not be fully written to SSD although the kernel thinks so? This is
That, and worse.
Incidently, I have just posted on my G+ about this:
https://plus.google.com/106981743284611658289/posts/Us8yjK9SPs6
which is mostly links to
http://lkcl.net/reports/ssd_analysis.html
https://www.usenix.org/conference/fast13/understanding-robustness-ssds-under-power-fault
After you read those, you'll never think twice about SSDs and data loss
anymore :-/
(I kind of found that out myself over time too, but these have much more
data than I got myself empirically on a couple of SSDs)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2013-12-30 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 21:11 Migrate to bcache: A few questions Kai Krakow
2013-12-30 1:03 ` Chris Murphy
2013-12-30 1:22 ` Kai Krakow
2013-12-30 3:48 ` Chris Murphy
2013-12-30 9:01 ` Marc MERLIN [this message]
2013-12-31 0:31 ` Kai Krakow
2013-12-30 6:24 ` Duncan
2013-12-31 3:13 ` Kai Krakow
2013-12-30 16:02 ` Austin S Hemmelgarn
2014-01-01 10:06 ` Duncan
2014-01-01 20:12 ` Austin S Hemmelgarn
2014-01-02 8:49 ` Duncan
2014-01-02 12:36 ` Austin S Hemmelgarn
2014-01-03 0:09 ` Duncan
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=20131230090125.GN19863@merlins.org \
--to=marc@merlins.org \
--cc=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).