From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <wagner@tansi.org>
Received: from tansi.org (ns.km10532-04.keymachine.de [87.118.102.195])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sun, 10 Jan 2010 20:48:49 +0100 (CET)
Received: from gatewagner.dyndns.org (84-74-164-239.dclient.hispeed.ch
	[84.74.164.239]) by tansi.org (Postfix) with ESMTP id 9DB40243069A
	for <dm-crypt@saout.de>; Sun, 10 Jan 2010 20:48:48 +0100 (CET)
Date: Sun, 10 Jan 2010 20:49:04 +0100
From: Arno Wagner <arno@wagner.name>
Message-ID: <20100110194904.GA5194@tansi.org>
References: <20100110151659.GA2635@tansi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100110151659.GA2635@tansi.org>
Subject: Re: [dm-crypt] renaming of 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: dm-crypt@saout.de

Just found out why I did not notice this before:
When the disk is not present at mount time, the 
respective entry is not created in /dev/scsi/
and you get the traditional output. I think
"status" should always give the traditional one 
as it has a fixed mapping between major/minor and 
device (see Documentation/devices.txt in the 
Linux sources), while the /dev/scsi/ entry has not.
Maybe have the device in /dev/scsi/ in addition, 
if present, e.g. like this:

root ~>cryptsetup status c1
/dev/mapper/c1 is active:
  cipher:  aes-cbc-essiv:sha256
  keysize: 256 bits
  device:  /dev/sdd (/dev/scsi/sdh4-0c0i0l0)
  offset:  0 sectors
  size:    1953525168 sectors
  mode:    read/write
root ~>

Arno


On Sun, Jan 10, 2010 at 04:16:59PM +0100, Arno Wagner wrote:
> Cryptsetup seems to report the device in /dev/scsi/*
> if they are present, instead of the device name 
> mappings were created with. So I created with /dev/sdd
> and status tells me I have /dev/scsi/sdh4-0c0i0l0,
> which is really a problem because it could cause me 
> to confuse devices and map them twice or the like.
> 
> Is there an easy way to map this back or turn off this
> behaviour or list both device names? What I do at the 
> moment is to look at major and minor of the reported 
> device and than look up which traditional device this 
> matches.
> 
> If this is a fundamental problem, I will likely
> write a wrapper (something like crypt-status)
> that does the lookup for me, but maybe there is 
> an easier solution?
> 
> Arno
> 
> -- 
> Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
> GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
> ----
> Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
> 
> If it's in the news, don't worry about it.  The very definition of 
> "news" is "something that hardly ever happens." -- Bruce Schneier 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
> 

-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier