From: Charles Cazabon <charlesc@pyropus.ca>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] luksFormat still spinning/hanging with large array on kernel 4.6.2
Date: Tue, 28 Jun 2016 12:48:43 -0600 [thread overview]
Message-ID: <20160628184843.GA19207@pyropus.ca> (raw)
In-Reply-To: <55fa4173-c7f4-a37a-78b7-bbd4ebff421e@gmail.com>
Milan Broz <gmazyland@gmail.com> wrote:
> On 06/28/2016 05:01 AM, Charles Cazabon wrote:
> > I've since moved the array over to another machine, also running Wheezy with
> > the mainline 4.6.2 kernel. cryptsetup luksFormat behaves the same there,
> > spinning forever and taking one full CPU.
[...]
> I need to verify that it is the same problem (if it is, then getrusage() call
> return all zeroed values).
[...]
> Just noticed this here - you are testing new cryptsetup binary but according
> to debug output it uses system old libcryptsetup library.
>
> Please use src/cryptsetup not directly src/.libs/cryptsetup ...
And this, indeed, fixed the problem. luksFormat completed in normal time.
Sorry, I wasn't sure which of the built `cryptsetup` files was the one to use
(in fact, I had assumed without checking that they would be hardlinks to the
same file).
Thanks muchly for the help. So whatever bug I hit is indeed the one you've
already fixed in newer versions.
Charles
--
------------------------------------------------------------------
Charles Cazabon <charlesc@pyropus.ca>
Software, consulting, and services available at http://pyropus.ca/
------------------------------------------------------------------
prev parent reply other threads:[~2016-06-28 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 19:16 [dm-crypt] [charlesc@pyropus.ca: Re: Does luksFormat write the full size of the device?] Charles Cazabon
2016-06-28 3:01 ` [dm-crypt] luksFormat still spinning/hanging with large array on kernel 4.6.2 Charles Cazabon
2016-06-28 6:39 ` Milan Broz
2016-06-28 18:48 ` Charles Cazabon [this message]
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=20160628184843.GA19207@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.