On 17.09.2015 at 21:43, Hugo Mills wrote:
On Thu, Sep 17, 2015 at 07:56:08PM +0200, Gert Menke wrote:
BTRFS looks really nice feature-wise, but is not (yet) optimized for
my use-case I guess. Disabling COW would certainly help, but I don't
want to lose the data checksums. Is nodatacowbutkeepdatachecksums a
feature that might turn up in the future?
[snip]
No. If you try doing that particular combination of features, you
end up with a filesystem that can be inconsistent: there's a race
condition between updating the data in a file and updating the csum
record for it, and the race can't be fixed.
I'm no filesystem expert, but isn't that what an intent log is for?
(Does btrfs have an intent log?)
And, is this also true for mirrored or raid5 disks?
I'm thinking something like "if the data does not match the checksum,
just restore both from mirror/parity" should be possible, right?
Gert
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
