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

On Sun, Dec 25, 2011 at 09:56:38PM -0700, Jeff Cook wrote:
> 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

Well, I am a little concerned because this is precisely my setup, 
however I have never had any problems. 
I have used it in two configurations: 

ext4 on top of dm-crypt (LUKS) on SSD

ext4 inside lvm on top of dm-crypt (LUKS) on SSD

Both have always worked perfectly for me, over a number of months at least.
I frequently manipulate large files such as ISO images, and often use rsync
to backup the whole filesystem, without trouble. 

eric

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

  reply	other threads:[~2011-12-26  5:38 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 [this message]
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=20111226053229.GA16362@limpoc.com \
    --to=epvdm@limpoc.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 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.