all of the auto-lvm bits are inside the lvm2 package or devmapper
packages; udev is unaffected
** Changed in: udev (Ubuntu)
Status: New = Invalid
--
[gutsy|hardy alpha4] `/etc/init.d/lvm2' missing
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a
Kay, the addition of ENV{DEVTYPE}==partition before calling vol_id in
persistent-storage.rules breaks LVM when the LVM PV is made across the
entire disk.
What was the rationale for adding that?
** Summary changed:
- [gutsy|hardy alpha4] `/etc/init.d/lvm2' missing
+ vol_id not run for
On Thu, 2008-04-10 at 15:33 +, Scott James Remnant wrote:
Kay, the addition of ENV{DEVTYPE}==partition before calling vol_id in
persistent-storage.rules breaks LVM when the LVM PV is made across the
entire disk.
What was the rationale for adding that?
Removable media devices will never
first I'm new to patching, etc; I don't know how to commit a fix to the
udev package, or even how to notify the package maintainer.
Well after a bunch of udev learning I have figured out why my desktop
install of lvm2 is not working.
the new udev rule for lvm2 is great, it depends on an
How were your LVs created? Do your LVs have UUIDs associated with them?
One way to check this is to look in /dev/disk/by-uuid and see whether or
not they are listed there.
In any case, I'll have a look at the LVM init script from Debian's
package and see what I can do.
--
[gutsy|hardy alpha4]
I just reinstalled with the desktop cd, after the libc6 disaster I had
reinstalled with the alt; hence removing my problem. No worries though
it's back for debugging.
Luke:
As I understand the lvm2 init.d script was removed because a udev rule was
added to replace
Sorry, should have tested that work-around before mentioning it;
modifying bootmisc.sh doesn't work as it is not called early enough in
the boot process.
--
[gutsy|hardy alpha4] `/etc/init.d/lvm2' missing
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a
I have a similar problem with lvm2. I install the daily alt hardy from
a couple days ago (just before alpha 5) on two of my computers. The
first had lv groups used for the root fs; all the lvs for this system
are activated properly on boot, things are great here. My second
computer only uses
I can confirm that this is still a problem in alpha5.
** Changed in: lvm2 (Ubuntu)
Status: New = Confirmed
--
[gutsy|hardy alpha4] `/etc/init.d/lvm2' missing
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a member of Ubuntu
Bugs, which is
