From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pamwdV-47urF for ; Thu, 25 Oct 2012 12:01:19 +0200 (CEST) Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 25 Oct 2012 12:01:19 +0200 (CEST) Received: by mail-ee0-f50.google.com with SMTP id c41so644118eek.37 for ; Thu, 25 Oct 2012 03:01:18 -0700 (PDT) Message-ID: <50890DE8.70705@gmail.com> Date: Thu, 25 Oct 2012 12:01:12 +0200 From: Milan Broz MIME-Version: 1.0 References: <5086225C.2010302@dennis.birkholz.biz> In-Reply-To: <5086225C.2010302@dennis.birkholz.biz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Force luksClose List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dennis Birkholz Cc: dm-crypt@saout.de 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