From: Jeff Cook <jeff@deserettechnology.com>
To: epvdm@limpoc.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 14:03:02 -0700 [thread overview]
Message-ID: <4EF8E106.600@deserettechnology.com> (raw)
In-Reply-To: <20111226053229.GA16362@limpoc.com>
On 12/25/2011 10:32 PM, epvdm@limpoc.com wrote:
> 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
>
> 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.
I appreciate your data point, thank you. I believe I am just going to
have to accept that this is hardware, even though I was hoping it was
software related since that's easier to handle.
Thanks again.
>
> eric
next prev parent reply other threads:[~2011-12-26 21:03 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 [this message]
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=4EF8E106.600@deserettechnology.com \
--to=jeff@deserettechnology.com \
--cc=dm-crypt@saout.de \
--cc=epvdm@limpoc.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