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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
