From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sat, 31 May 2014 10:32:30 +0200 (CEST) Date: Sat, 31 May 2014 10:32:28 +0200 From: Heinz Diehl Message-ID: <20140531083228.GA3141@fancy-poultry.org> References: <20140530134238.GA21698@tansi.org> <20140530150701.GA4281@fancy-poultry.org> <5388AA9C.3020909@codehawks.eu> <20140530171053.GA5729@fancy-poultry.org> <5388BED0.90203@codehawks.eu> <20140530174743.GA6376@fancy-poultry.org> <5388C67D.1060004@codehawks.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5388C67D.1060004@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: > > As far as I know, mkfs discards blocks while creating the filesystem. > > So your device should be "overwritten" at that stage of the process? > Oh cool. I had no idea. So then it would make the whole dd operation > useless if you pass --allow-discards to cryptsetup. I think so. At least mkfs.xfs, mkfs.ext4 and mkfs.btrfs are discarding blocks while creating the fs. Don't know about other fs.