From: Neuer User <auslands-kv@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs und lvm-cache?
Date: Wed, 23 Dec 2015 12:38:16 +0100 [thread overview]
Message-ID: <n5e139$r1h$1@ger.gmane.org> (raw)
In-Reply-To: <1527885.5NheBqth0k@merkaba>
Am 23.12.2015 um 12:21 schrieb Martin Steigerwald:
> Hi.
>
> As far as I understand this way you basically loose the RAID 1 semantics of
> BTRFS. While the data is redundant on the HDDs, it is not redundant on the
> SSD. It may work for a pure read cache, but for write-through you definately
> loose any data integrity protection a RAID 1 gives you.
>
Hmm, are you sure? I thought LVM lies underneath btrfs. Btrfs thus
should not know about the caching SSD at all. It only knows of the two
LVs on the HDDs, reading and writing data from or to one or both of the
two LVs.
Only then lvmcache decides if it reads the data from the underlying HDD
or from the cache ssd. LVM shouldn't even know that the two LVs are
configured as RAID1 on btrfs as this is a level higher. So for LVM the
two LVs are diffeent data, both of which would need to be cached
independently on the SDD.
What might happen though, is that there is a data loss on the SDD,
returning a mismatching checksum, so btrfs might think that the data is
incorrect on one LV (=HDD), although it is indeed correct there. That
would lead btrfs to read the data from the second LV (which might also
be in the SDD cache or not) and then updating the (correct and
identical) data of the first LV with it.
Or do I see that wrong?
> Of course, you can use two SSDs and have them work as RAID 1 as well.
>
> There is a patch set for in-BTRFS SSD-caching. It consists of a patch set to
> add hot data tracking to VFS and a patch set for adding support in BTRFS. But
> I didn´t see anything of these in quite some time.
That would be interesting, but for my project it's probably too late.
>
> Happy christmas,
>
Yeah, happy christmas to you and eveybody on the list.
Michael
next prev parent reply other threads:[~2015-12-23 11:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:45 btrfs und lvm-cache? Neuer User
2015-12-23 11:21 ` Martin Steigerwald
2015-12-23 11:38 ` Neuer User [this message]
2015-12-23 19:45 ` Noah Massey
2015-12-23 20:07 ` Neuer User
2015-12-23 20:38 ` Holger Hoffstätte
2015-12-23 19:49 ` Chris Murphy
2015-12-23 20:21 ` Neuer User
2015-12-23 20:56 ` Chris Murphy
2015-12-24 15:19 ` Neuer User
2015-12-23 20:24 ` Neuer User
2015-12-23 20:59 ` Chris Murphy
2015-12-24 2:04 ` Duncan
2015-12-24 15:24 ` Neuer User
2015-12-24 14:56 ` Piotr Pawłow
2015-12-24 15:29 ` Neuer User
2015-12-24 16:42 ` Piotr Pawłow
2015-12-25 17:11 ` Neuer User
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='n5e139$r1h$1@ger.gmane.org' \
--to=auslands-kv@gmx.de \
--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 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.