DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Boyhan <adamb@medent.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] dm-crypt + mdadm
Date: Fri, 22 Nov 2013 11:29:57 -0500 (EST)	[thread overview]
Message-ID: <1083384064.30141.1385137797930.JavaMail.root@medent.com> (raw)
In-Reply-To: <942152294.28287.1385136420109.JavaMail.root@medent.com>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

Doing allot of testing with dm-crypt and mdadm. Running into an issues which is killing me. We run a standard CentOS6 load with kernel "2.6.32-358.23.2.el6.x86_64" 

Scenario #1: mdadm raid10 -> dm-crypt -> ext4 
Scenario #2: dm-crypt -> mdadm raid10 -> ext4 

Scenario #1 has no issues and runs reliably but takes a significant hit in performance due to the single threaded nature of kryptd. I read quite a bit about people instead encrypting each block device then putting software encryption on that. This all goes well until I start to benchmark. The writing process of the benchmark goes well, as soon as I hit the read portion of the test, the machine panics and locks up. I initially tested this idea with raid0 and I don't have this panic, it seems that only raid10 causes the panic. At this point I am stumped as to what I can do. I am feel this is more an issue with mdadm than dm-crypt but I figured it was worth getting others opinions. I appreciate any or all help, if I am missing any details let me know and I will provide them. 

Thanks, 
Adam Boyhan 



[-- Attachment #2: Type: text/html, Size: 1392 bytes --]

       reply	other threads:[~2013-11-22 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <942152294.28287.1385136420109.JavaMail.root@medent.com>
2013-11-22 16:29 ` Adam Boyhan [this message]
2013-11-22 22:53   ` [dm-crypt] dm-crypt + mdadm Arno Wagner
2013-11-23  8:10     ` Milan Broz
2013-11-23 11:58       ` Arno Wagner
2013-11-23 13:29         ` Milan Broz

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=1083384064.30141.1385137797930.JavaMail.root@medent.com \
    --to=adamb@medent.com \
    --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