191316 – sys-fs/udev-115 , sys-fs/device-mapper-1.02.22 mount-problem with dmcrypt

Bug 191316 - sys-fs/udev-115 , sys-fs/device-mapper-1.02.22 mount-problem with dmcrypt

Summary: sys-fs/udev-115 , sys-fs/device-mapper-1.02.22 mount-problem with dmcrypt

Status:	RESOLVED DUPLICATE of bug 190819

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	AMD64 Linux

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-09-05 00:56 UTC by Jochen Schlick
Modified:	2007-09-07 15:55 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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 ***