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 1D8jnadu98aL for ; Fri, 1 Jun 2012 15:00:52 +0200 (CEST) Received: from mail-bk0-f50.google.com (mail-bk0-f50.google.com [209.85.214.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 1 Jun 2012 15:00:52 +0200 (CEST) Received: by bkcjg9 with SMTP id jg9so2519186bkc.37 for ; Fri, 01 Jun 2012 06:00:51 -0700 (PDT) Message-ID: <4FC8BCFF.2010904@gmail.com> Date: Fri, 01 Jun 2012 15:00:47 +0200 From: Milan Broz MIME-Version: 1.0 References: <20120601055524.GA27280@tansi.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] inconsistency in opening multiple mappers on the same device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." Cc: dm-crypt@saout.de On 06/01/2012 02:47 PM, .. ink .. wrote: > The error should have said "mapper name zzz already exist", not > "device zzz already exist". Device-mapper create block DEVICES. "mapper name" means nothing, It is "device-mapper device name" if you want to be precise. Milan