From: Emmanuel Florac <eflorac@intellique.com>
To: FERNANDO FREDIANI <fernando.frediani@upx.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: SSD usage for bcache - Read and Writeback
Date: Thu, 14 Sep 2017 17:04:00 +0200 [thread overview]
Message-ID: <20170914170400.3463da66@harpe.intellique.com> (raw)
In-Reply-To: <CAD7b65Lcc+soTr2bLuCoseQR8CLfmSfXE-oXQUxvJMCxH+Znfg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Le Thu, 14 Sep 2017 11:46:11 -0300
FERNANDO FREDIANI <fernando.frediani@upx.com> écrivait:
> Not really mandatory but optional.
>
> From bcache documentation:
>
> "In the event of a data IO error on the flash it will try to recover
> by reading from disk or invalidating cache entries. For
> unrecoverable errors (meta data or dirty data), caching is
> automatically disabled; if dirty data was present in the cache it
> first disables writeback caching and waits for all dirty data to be
> flushed."
If the cache is dirty and has failed, your data is lost or corrupted
all the same. The way a SSD fails is usually one second it works, the
next second it's as dead as a rock. If you're using it as a write
cache, whatever amount of data is dirty is lost. If it's 8 GB, you've
lost your last 8 GB of writes, often very important filesystem metadata
and/or database journal, i.e. your data is completely hosed.
Don't use SSDs as write cache without RAID-1 (or use very expensive,
redundant NVMe SSDs only), unless your data isn't very important.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-09-14 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 14:04 SSD usage for bcache - Read and Writeback FERNANDO FREDIANI
2017-09-14 7:58 ` Coly Li
2017-09-14 11:43 ` Kai Krakow
2017-09-14 13:10 ` FERNANDO FREDIANI
2017-09-14 14:40 ` Emmanuel Florac
2017-09-14 14:46 ` FERNANDO FREDIANI
2017-09-14 15:04 ` Emmanuel Florac [this message]
2017-09-14 15:11 ` FERNANDO FREDIANI
2017-09-14 14:45 ` Coly Li
2017-09-14 14:54 ` FERNANDO FREDIANI
2017-09-14 15:04 ` Coly Li
2017-09-14 15:14 ` FERNANDO FREDIANI
2017-09-26 19:28 ` FERNANDO FREDIANI
2017-09-26 19:51 ` Michael Lyle
2017-09-26 20:02 ` FERNANDO FREDIANI
2017-09-26 20:27 ` Kai Krakow
2017-09-14 15:31 ` Kai Krakow
2017-09-14 15:49 ` Coly Li
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=20170914170400.3463da66@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=fernando.frediani@upx.com \
--cc=linux-bcache@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