From: Charles Cazabon <charlesc@pyropus.ca>
To: dm-crypt@saout.de
Subject: [dm-crypt] Does luksFormat write the full size of the device?
Date: Sat, 25 Jun 2016 21:39:01 -0600 [thread overview]
Message-ID: <20160626033901.GA10467@pyropus.ca> (raw)
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 <charlesc@pyropus.ca>
Software, consulting, and services available at http://pyropus.ca/
------------------------------------------------------------------
next reply other threads:[~2016-06-26 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 3:39 Charles Cazabon [this message]
2016-06-26 10:46 ` [dm-crypt] Does luksFormat write the full size of the device? Milan Broz
2016-06-26 15:02 ` Charles Cazabon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160626033901.GA10467@pyropus.ca \
--to=charlesc@pyropus.ca \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.