All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cook <jeff@deserettechnology.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] dm-crypt on SSD gives regular file corruption and segfaults
Date: Sun, 25 Dec 2011 21:56:38 -0700	[thread overview]
Message-ID: <4EF7FE86.2060901@deserettechnology.com> (raw)

Hello.

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.

From
Jeff
-- 
Jeff Cook
jeff@deserettechnology.com

             reply	other threads:[~2011-12-26  4:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26  4:56 Jeff Cook [this message]
2011-12-26  5:32 ` [dm-crypt] dm-crypt on SSD gives regular file corruption and segfaults epvdm
2011-12-26 21:03   ` Jeff Cook
2011-12-27  7:46     ` Arno Wagner
2011-12-26  9:05 ` 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=4EF7FE86.2060901@deserettechnology.com \
    --to=jeff@deserettechnology.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.