From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt on SSD gives regular file corruption and segfaults
Date: Tue, 27 Dec 2011 08:46:12 +0100 [thread overview]
Message-ID: <20111227074611.GA3652@tansi.org> (raw)
In-Reply-To: <4EF8E106.600@deserettechnology.com>
Corruption and crashes in combination are almost always
RAM and sometimes CPU (overclocked), mainboard and PSU
(old or low-quality).
For this reason there is a long text in the cryptsetup
FAQ section on troubleshooting that deals with testing
RAM.
Not nice, as the only wa to fix this is replacement
(and I know that quite a few people cannot just pay
for new RAM without thinking about where to get the
money), but a fact of consumer-grade hardware.
Arno
On Mon, Dec 26, 2011 at 02:03:02PM -0700, Jeff Cook wrote:
> 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
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2011-12-27 7:46 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 [this message]
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=20111227074611.GA3652@tansi.org \
--to=arno@wagner.name \
--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.