From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Christian Hesse <mail@earthworm.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dm(-crypt) and /dev/disk/by-label/
Date: Mon, 14 May 2007 19:06:15 +0600 [thread overview]
Message-ID: <46485EC7.8040006@ums.usu.ru> (raw)
In-Reply-To: <200705141348.48099.mail@earthworm.de>
Christian Hesse wrote:
> Hello everybody,
>
> If this is the wrong place to ask, please tell me where to ask instead.
linux-hotplug-devel, but they will tell you to ask your distro vendor.
> I have ext3 filesystems with labels on devicemapper crypted devices. These do
> not show up in /dev/disk/by-label/, in contrast to filesystems of my "real"
> partitions. Is this the expected behaviour or what could go wrong?
Some distributions intentionally tell udev to ignore device-mapper devices
completely, for the following reasons:
1) without this prohibition, udev creates /dev/dm-* devices, and LILO breaks
completely if they are present instead of the correct /dev/mapper/* nodes
created by dmsetup and similar tools
2) without this prohibition, udev tries to open snapshot devices managed by
dm-snapshot. The problem is that LVM2 sometimes creates such snapshots with
the intention just to see whether it can be done. Udev keeps the temporary
device open and thus prevents LVM2 from removing the temporary snapshot cleanly.
More details can be found at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401393
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392623
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343671
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344040
Since the only known way to solve the above problems at that time was to
prevent udev from looking at device-mapper, crypted devices don't show up in
/dev/disk/by-label/ on your system.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2007-05-14 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 11:48 dm(-crypt) and /dev/disk/by-label/ Christian Hesse
2007-05-14 13:06 ` Alexander E. Patrakov [this message]
2007-05-14 19:55 ` Jan Engelhardt
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=46485EC7.8040006@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@earthworm.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.