From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Fri, 30 May 2014 19:47:45 +0200 (CEST) Date: Fri, 30 May 2014 19:47:43 +0200 From: Heinz Diehl Message-ID: <20140530174743.GA6376@fancy-poultry.org> References: <1401370403.94216.YahooMailNeo@web172002.mail.ir2.yahoo.com> <20140529201335.GA9014@tansi.org> <20140530134238.GA21698@tansi.org> <20140530150701.GA4281@fancy-poultry.org> <5388AA9C.3020909@codehawks.eu> <20140530171053.GA5729@fancy-poultry.org> <5388BED0.90203@codehawks.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5388BED0.90203@codehawks.eu> Subject: Re: [dm-crypt] Is erasing hard disk drive mandatory? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 30.05.2014, Thomas Bastiani wrote: > It may be that files that you create and then delete will trigger > a TRIM operation if dm-crypt (and > eventually LVM) are configured to pass TRIM through. But the rest of > your "securely erased" drive is still not TRIM-ed. As far as I know, mkfs discards blocks while creating the filesystem. So your device should be "overwritten" at that stage of the process? (I for myself never do any overwriting of harddisks, I've just asked out of sheer curiosity).