DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Dennis Birkholz <dm-crypt@dennis.birkholz.biz>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Force luksClose
Date: Thu, 25 Oct 2012 12:01:12 +0200	[thread overview]
Message-ID: <50890DE8.70705@gmail.com> (raw)
In-Reply-To: <5086225C.2010302@dennis.birkholz.biz>

On 10/23/2012 06:51 AM, Dennis Birkholz wrote:
> I am using a crypt mapping on a Software-RAID5. As my raid crashed (2 of
> 5 drives disappeared), I was not able to remove the crypt mapping
> because the raid device was not accessible any more. It would be nice to
> have a force option so the mapping is removed and I can stop the
> degraded raid. The only option was to reboot which is not a very good
> solution.

The luksClose / remove should remove mapping if underlying device disappeared.

But there was some bug related to this - which cryptsetup version you are using?

Anyway, you can always use "dmsetup remove" and if it fails, "dmsetup remove -f"
(The second will replace mapping with error target, so you can force detach
even used device.)

Milan

  reply	other threads:[~2012-10-25 10:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  4:51 [dm-crypt] Force luksClose Dennis Birkholz
2012-10-25 10:01 ` Milan Broz [this message]
2012-10-25 14:46   ` Dennis Birkholz
  -- strict thread matches above, loose matches on Subject: below --
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
2013-02-22  0:17           ` Benjamin Eberhardt
2015-11-29 18:42 yac

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=50890DE8.70705@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@dennis.birkholz.biz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox