From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] renaming of device
Date: Sun, 10 Jan 2010 20:49:04 +0100 [thread overview]
Message-ID: <20100110194904.GA5194@tansi.org> (raw)
In-Reply-To: <20100110151659.GA2635@tansi.org>
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
next prev parent reply other threads:[~2010-01-10 19:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 15:16 [dm-crypt] renaming of device Arno Wagner
2010-01-10 19:49 ` Arno Wagner [this message]
2010-01-10 20:33 ` Milan Broz
2010-01-11 16:17 ` Arno Wagner
2010-01-13 7:01 ` Luca Berra
2010-01-13 10:20 ` Sven Eschenberg
2010-01-13 13:13 ` Arno Wagner
2010-01-13 16:18 ` Sven Eschenberg
2010-01-13 17:29 ` Arno Wagner
2010-01-14 18:18 ` Sven Eschenberg
2010-01-14 21:42 ` Arno Wagner
2010-01-14 22:16 ` Sven Eschenberg
2010-01-14 22:46 ` Arno Wagner
2010-01-15 2:17 ` Sven Eschenberg
2010-01-15 3:58 ` Arno Wagner
2010-01-15 11:28 ` Sven Eschenberg
2010-01-16 0:30 ` Ross Boylan
2010-01-16 2:46 ` Arno Wagner
2010-01-16 8:39 ` Milan Broz
2010-01-16 16:22 ` Arno Wagner
2010-01-16 18:52 ` Sven Eschenberg
2010-01-18 14:06 ` Milan Broz
2010-01-18 14:58 ` Sven Eschenberg
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=20100110194904.GA5194@tansi.org \
--to=arno@wagner.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.