DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Krainz <ldm@gmx.at>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] btrfs with raid5/6
Date: Wed, 27 Oct 2010 17:14:32 +0200	[thread overview]
Message-ID: <4CC841D8.8000709@gmx.at> (raw)
In-Reply-To: <20101027144102.GB10534@fancy-poultry.org>


> It's up to you. I'd prefer LUKS/dmcrypt.
So do I. But I have a related concern:

I currently do ext4 <-> dm-crypt <-> linux-software-raid <-> hdds

However Linux Software Raid (mdadm) does not protect you from silent 
data loss, because it does not store checksums in it's metadata.
So what mdadm does is, it compensates for failed devices, or blocks, if 
the device reports them as bad. But I can NOT correct data, that was 
e.g. corrupted by the SATA controller or backplane.
See http://neil.brown.name/blog/20100211050355 "Smart or simple RAID 
recovery??" for more information.

Btrfs (like ZFS) can be the solution here, as it stores CRC checksums 
with all data and metadata. RAID5 with protection from silent data loss 
is promised to be implemented in the future.
A setup on top of dm-crypt would look as follows:

btrfs <-> multiple dm-crypt partitions <-> multiple devices

However in the past I experienced very disappointing results, if raid is 
running on top of dm-crypt partitions.
If I remove hdds from such a setup the dm-crypt partition wont 
disappear. It won't propagate the error to the software raid on top of 
it (not familiar with the implementation details, maybe mdadm is to 
blame here).
And finally it won't even let itself be deleted without restart (I think 
the last issue has been fixed in the meantime).

I urge the dm-crypt developers to improve this situation with raid on 
top of dm-crypt, be it with mdadm or btrfs.
Solutions for other long-time annoying issues like insufficient 
threading support, and the lack of discard support, would be appreciated 
too. :P
I know the OSS pradigm is provide patches yourself. Would you be 
accepting patches?

Sincerly,
Markus

      reply	other threads:[~2010-10-27 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 12:54 [dm-crypt] btrfs M Thomas Frederiksen
2010-10-27 12:59 ` Christoph Anton Mitterer
2010-10-27 14:10   ` Arno Wagner
2010-10-27 14:15     ` Christoph Anton Mitterer
2010-10-27 14:18       ` Arno Wagner
2010-10-27 23:19     ` Paul Dugas
2010-10-27 14:41 ` Heinz Diehl
2010-10-27 15:14   ` Markus Krainz [this message]

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=4CC841D8.8000709@gmx.at \
    --to=ldm@gmx.at \
    --cc=dm-crypt@saout.de \
    /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