From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: linux-hotplug@vger.kernel.org
Subject: udev by-label/by-uuid vs. lvm2
Date: Thu, 02 Nov 2006 17:05:10 +0000 [thread overview]
Message-ID: <454A2546.9040808@ciphirelabs.com> (raw)
Hi,
not sure if this is an ubuntu issue:
at least on ubuntu edgy udev creates the
usual /dev/disk/by-uuid and by-label directories
with links for all filesystems/disks/partitions.
but with lvm2 vg's are only created in
/dev/<foo>/<bar> and /dev/mapper/<foo>-<bar>.
that is ok, <foo> is the pv and <bar> the vg.
still the filesystem on <bar> has a uuid and
a label, and neither is found in /dev/disk/by-*/
as link. As a result booting with LABEL or UUID
doesn't work in the initramfs either (UUID is
the default config as far as I know).
can someone tell me if this problem is
a) wontfix/by design
b) kernel too old problem (maybe lvm2 doesn't
create events for udev?)
c) udev out of date or misconfigured (so I will
file a bug with ubuntu to let them know)
d) something else
Thanks, Andreas
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2006-11-02 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 17:05 Andreas Jellinghaus [this message]
2006-11-02 17:38 ` udev by-label/by-uuid vs. lvm2 Bryan Kadzban
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=454A2546.9040808@ciphirelabs.com \
--to=aj@ciphirelabs.com \
--cc=linux-hotplug@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).