From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from detritus.pyropus.ca (detritus.pyropus.ca [64.5.53.58]) by mail.server123.net (Postfix) with SMTP for ; Sun, 26 Jun 2016 05:46:11 +0200 (CEST) Date: Sat, 25 Jun 2016 21:39:01 -0600 From: Charles Cazabon Message-ID: <20160626033901.GA10467@pyropus.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [dm-crypt] Does luksFormat write the full size of the device? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hi, I'm currently initializing a fairly large LUKS crypt device, about 33TiB. I've done this before, but not for quite a while, so I can't remember how long it normally takes. My current cryptsetup invocation has been running for about 24 hours, taking 100% of one CPU core for that entire time. If there's I/O happening, iostat isn't showing it. If `cryptsetup luksFormat` has to write the entire contents of the underlying block device, then this length of time is reasonable - but I don't recall if it has to do that. Is this long runtime normal for initialization of a device of this size? System is Debian Wheezy with a mainline 4.6.2 kernel, cryptsetup 1.4.3 from the normal Debian package. Thanks, Charles -- ------------------------------------------------------------------ Charles Cazabon Software, consulting, and services available at http://pyropus.ca/ ------------------------------------------------------------------