From: Matthias Schniedermeyer <ms@citd.de>
To: Benjamin Eberhardt <eberhab@gmail.com>
Cc: dm-crypt@saout.de, Milan Broz <gmazyland@gmail.com>
Subject: Re: [dm-crypt] force luksClose
Date: Thu, 21 Feb 2013 23:08:52 +0100 [thread overview]
Message-ID: <20130221220852.GA23353@citd.de> (raw)
In-Reply-To: <CAPrQCgaVPnJwgFTHtzjRnnBLCqEugpMfFjMdrmvjuvV8a0g+JQ@mail.gmail.com>
On 21.02.2013 22:16, Benjamin Eberhardt wrote:
> Hi all,
>
> the aboved mentioned problem happened to me again and this time i made sure
> i would try to find every open file and close it first, then unmount the
> partition but still luksClose did not work...
>
> The partition is unmounted but still i get this error:
>
> # 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)
From my personal experience the things that DON'T show up in lsof are:
mountpoints (and bind-mounts)
nfs
So if there is a mountpoint inside, you have to umount that first. If
you have a NFS-export of the mountpoint or something inside the
mountpoint you have to remove that export or stop NFS for the moment it
takes to do the umount.
There may be other things that don't show up in lsof, but i don't know
about them.
--
Matthias
next prev parent reply other threads:[~2013-02-21 22:08 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 [this message]
2013-02-21 22:41 ` Milan Broz
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=20130221220852.GA23353@citd.de \
--to=ms@citd.de \
--cc=dm-crypt@saout.de \
--cc=eberhab@gmail.com \
--cc=gmazyland@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 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.