From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nv01t-Qzs7tz for ; Mon, 26 Dec 2011 05:56:29 +0100 (CET) Received: from mail-iy0-f178.google.com (mail-iy0-f178.google.com [209.85.210.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 26 Dec 2011 05:56:28 +0100 (CET) Received: by iagf6 with SMTP id f6so21839704iag.37 for ; Sun, 25 Dec 2011 20:56:27 -0800 (PST) Sender: Jeff Cook Message-ID: <4EF7FE86.2060901@deserettechnology.com> Date: Sun, 25 Dec 2011 21:56:38 -0700 From: Jeff Cook MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: [dm-crypt] dm-crypt on SSD gives regular file corruption and segfaults Reply-To: jeff@deserettechnology.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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