From: Milan Broz <gmazyland@gmail.com>
To: Mrukant Popat <mrukant@gmail.com>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] cryptsetup 1.6.2 hands on "waiting for zero"
Date: Mon, 04 May 2015 21:05:27 +0200 [thread overview]
Message-ID: <5547C2F7.3000305@gmail.com> (raw)
In-Reply-To: <CADDQthuKj7zH-kT14WX4R0m85C_1ANng3Jp-ijSEtzg626yqFA@mail.gmail.com>
On 05/04/2015 08:56 PM, Mrukant Popat wrote:
> Dear All,
>
> I am using cryptsetup 1.6.2 on a freescale imx6 processor. However when I run "cryptsetup -v --debug luksFormat /dev/sdb1" it hangs. Below is the output.
...
>
> # Udev cookie 0xd4d2ea2 (semid 0) decremented to 1
>
> # Udev cookie 0xd4d2ea2 (semid 0) waiting for zero
In fact this has nothing to do with cryptsetup itself, it is device-mapper library internals.
Usually it means misconfiguration of libdevmapper installation or wrong or missing device-mapper udev rules.
Do you compile it yourself? What distro is it?
Milan
next prev parent reply other threads:[~2015-05-04 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 18:56 [dm-crypt] cryptsetup 1.6.2 hands on "waiting for zero" Mrukant Popat
2015-05-04 19:05 ` Milan Broz [this message]
2015-05-04 19:29 ` Mrukant Popat
2015-05-04 19:40 ` Milan Broz
2015-05-04 19:56 ` Mrukant Popat
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=5547C2F7.3000305@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=mrukant@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox