DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: jeff@deserettechnology.com
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt on SSD gives regular file corruption and segfaults
Date: Mon, 26 Dec 2011 10:05:31 +0100	[thread overview]
Message-ID: <4EF838DB.20503@redhat.com> (raw)
In-Reply-To: <4EF7FE86.2060901@deserettechnology.com>

On 12/26/11 05:56, Jeff Cook wrote:
> I'm not sure if the cause of this is the SSD or dm-crypt or what, but I
> thought I would ask here if anyone had similar problems. My SSD with
> ext4 and dm-crypt experiences significant corruptions and frequent,
> seemingly-random segfaults. Data transferred to my disk will offer
> different md5sums and sometimes large things consider themselves
> corrupted. Has anyone experience things on dm-crypt or SSD? I am just
> curious if this should be attributed to the dm-crypt software layer or
> if I need to start looking more into the hardware.

Check your hw first - mainly SSD and RAM.
I saw several such corruptions on SSD recently and it was always hw related.

You will probably see the same problem even if you use your disk directly
without dmcrypt, just not so often - encryption usually makes small
data corruption worse because of error distribution during encryption
(one corrupted bit in underlying device  -> at least 16 byte block 
corrupted after decryption - for fs bitmap array this is fatal error).

Milan

      parent reply	other threads:[~2011-12-26  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26  4:56 [dm-crypt] dm-crypt on SSD gives regular file corruption and segfaults Jeff Cook
2011-12-26  5:32 ` epvdm
2011-12-26 21:03   ` Jeff Cook
2011-12-27  7:46     ` Arno Wagner
2011-12-26  9:05 ` Milan Broz [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=4EF838DB.20503@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=jeff@deserettechnology.com \
    /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