From: Milan Broz <gmazyland@gmail.com>
To: Benjamin Eberhardt <eberhab@gmail.com>
Cc: dm-crypt@saout.de, Matthias Schniedermeyer <ms@citd.de>,
Milan Broz <gmazyland@gmail.com>
Subject: Re: [dm-crypt] force luksClose
Date: Thu, 21 Feb 2013 23:41:31 +0100 [thread overview]
Message-ID: <5126A29B.2080604@gmail.com> (raw)
In-Reply-To: <CAPrQCgaVPnJwgFTHtzjRnnBLCqEugpMfFjMdrmvjuvV8a0g+JQ@mail.gmail.com>
On 21.2.2013 22:16, Benjamin Eberhardt wrote:
>
> # cryptsetup luksClose sata_p1_2TBa
> Device sata_p1_2TBa is busy.
>
> no open files on *sata* davice (both device and mountpoint are called the same)
>
> # lsof |grep sata
> #
>
> blkid doesnt really help me either:
>
> # lsblk
There must be something wrong with that device,
it must show in lsblk output (but it is not there).
Seems like it is partially removed (empty table) - can you add
output of
dmsetup table sata_p1_2TBa
dmsetup info -c sata_p1_2TBa
blockdev --getsz /dev/mapper/sata_p1_2TBa ?
(btw another mapping will not show in lsof, but it should
be visible in lsblk. If it is reproducible I would like to at least
fix lsblk so we have some reliable tool to debug it...)
Milan
next prev parent reply other threads:[~2013-02-21 22:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 13:02 [dm-crypt] force luksClose Benjamin Eberhardt
2012-11-29 13:43 ` Matthias Schniedermeyer
2012-11-29 14:53 ` Milan Broz
2012-12-25 12:17 ` Benjamin Eberhardt
2013-02-21 21:16 ` Benjamin Eberhardt
2013-02-21 22:08 ` Matthias Schniedermeyer
2013-02-21 22:41 ` Milan Broz [this message]
2013-02-22 0:17 ` Benjamin Eberhardt
-- strict thread matches above, loose matches on Subject: below --
2015-11-29 18:42 yac
2012-10-23 4:51 [dm-crypt] Force luksClose Dennis Birkholz
2012-10-25 10:01 ` Milan Broz
2012-10-25 14:46 ` Dennis Birkholz
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=5126A29B.2080604@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=eberhab@gmail.com \
--cc=ms@citd.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.