From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Tue, 18 Jan 2011 10:35:01 +0100 (CET)
Message-ID: <4D355EC0.6090402@redhat.com>
Date: Tue, 18 Jan 2011 10:34:56 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <20110118090149.GE14608@jeru.org>
In-Reply-To: <20110118090149.GE14608@jeru.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] From /dev/mapper to the real device
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: nicollet@jeru.org
Cc: dm-crypt@saout.de

On 01/18/2011 10:01 AM, Xavier Nicollet wrote:
> I did something like that:
> cryptsetup luksOpen /dev/mapper/lv_device crypto_device
> 
> I would like to find a way, given /dev/mapper/crypto_device, to find
> which lv_device it was built from.

cryptsetup status crypto_device (for active mapping)?

(But note this device name is not always the same you used, for LV you can
have several symlinks /dev/mapper/vg-lv or /dev/vg/lv or /dev/by-uuid/... 
so there are hardcoded priorities)

Milan