From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ms@citd.de>
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 hj86EtjMTuDy for <dm-crypt@saout.de>;
 Wed, 16 Jan 2013 13:00:31 +0100 (CET)
Received: from awesome.dsw2k3.info (awesome.dsw2k3.info
 [IPv6:2a01:198:661:1f::3])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 16 Jan 2013 13:00:31 +0100 (CET)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by awesome.dsw2k3.info (Postfix) with ESMTP id 57509C01C2
 for <dm-crypt@saout.de>; Wed, 16 Jan 2013 13:00:30 +0100 (CET)
Received: from awesome.dsw2k3.info ([127.0.0.1])
 by localhost (awesome.dsw2k3.info [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id zRvmm+3NVb4X for <dm-crypt@saout.de>;
 Wed, 16 Jan 2013 13:00:28 +0100 (CET)
Received: from citd.de (p4FC4D259.dip.t-dialin.net [79.196.210.89])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by awesome.dsw2k3.info (Postfix) with ESMTPSA
 for <dm-crypt@saout.de>; Wed, 16 Jan 2013 13:00:28 +0100 (CET)
Date: Wed, 16 Jan 2013 13:00:26 +0100
From: Matthias Schniedermeyer <ms@citd.de>
Message-ID: <20130116120026.GA16868@citd.de>
References: <CAFRU1Xvk8oH-vgy4qWDj7PPhankZQMzNaB7+uLk2Tr-vOpvE=g@mail.gmail.com>
 <20130116112321.GA6637@tansi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130116112321.GA6637@tansi.org>
Subject: Re: [dm-crypt] Memory errors and and 3TB RAID5 partition
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 16.01.2013 12:23, Arno Wagner wrote:
> Hi Frederico,
> 
> An alternative is to verify each write. Here you have to be careful
> to empty all buffers and caches before doing it. That is what I
> do for large files. 

My M.O. is to make MD5(*) sums of just about every file. So after i move 
files around, i just verify the MD5 sums. The amount of data moved is 
usually (a lot) bigger than available RAM, so i usually forgo clearing 
the cache, otherwise i do a umount/mount-cycle before verifying the MD5 
sums.

I'm doing this since a few years ago when i had trouble with a 
particular USB2<->Sata chip that had a rare tendency to corrupt a 
specific bit-pattern every now and then. Since then i had never any 
trouble with data-corruption.



*:
This case doesn't concern security, so MD5 is "good enough".

-- 

Matthias