Bug 191316

Summary:	sys-fs/udev-115 , sys-fs/device-mapper-1.02.22 mount-problem with dmcrypt
Product:	Gentoo Linux	Reporter:	Jochen Schlick <josch09>
Component:	[OLD] Core system	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	Jan.Schubert
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Jochen Schlick 2007-09-05 00:56:42 UTC

Hi, 
I use a script to mount a dmcrypt-loop-file for my private data containing the following commands (extracted from the script which use variables and does some additional error checking and other non important things):
 
>/sbin/losetup /dev/loop0 /PmntDevFile
>/usr/bin/gpg --no-mdc-warning --quiet -d /Pmnt.key.gpg | /sbin/cryptsetup -h plain -c aes-cbc-essiv:sha256 create PmntMAP /dev/loop0
>/bin/mount -t ext3 -o user -o noatime /dev/mapper/PmntMAP /Pmnt

--> after the mount command I expect that mount without params show the following:
>mount
/dev/mapper/PmntMAP on /Pmnt type ext3 (rw,noexec,nosuid,nodev,noatime)
..

but the result is most of the time (not deterministic!!!!):
/dev/dm-0 on /Pmnt type ext3 (rw,noexec,nosuid,nodev,noatime)
... 

What does udev in this case? the device name is PmntMAP and I and other tools expect that the mount-device is /dev/mapper/PmntMAP and not /dev/dm-0.

Reproducible: Sometimes

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2007-09-05 05:44:14 UTC


*** This bug has been marked as a duplicate of bug 190819 ***