*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213
Wow, don't know which is sadder...that the age of this problem, or that
it took me this long to finally do a search on this problem.
Instead I've been trying to allow for reboots after unattended upgrades
t
*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213
** This bug has been marked a duplicate of bug 1396213
LVM VG is not activated during system boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
@Brian Funny. You think three months to triage is long? Well, I reported
this very bug in April 2009...
https://bugs.launchpad.net/lvm2/+bug/360237
Your move :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I have pretty much the same problem. Once a snapshot is on the volume,
the system fails to boot.
the problem is exactly as described here: http://www.redhat.com/archives
/linux-lvm/2012-February/msg00028.html and the people on the mailing
list suggest broken udev rules.
fstab is pretty normal:
#
What is the contents of /etc/fstab ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995645
Title:
udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y''
To manage no
as of lvm2 2.02.98-6ubuntu1 the bug is still here. It may appear only if
you have snapshots LVs.
It seems to be caused by this udev rule: /lib/udev/rules.d/85-lvm2.rules
It should be noted that this file is not present in Debian's lvm2
2.02.98-6.
This persons says that commenting this rule remov
guilty udev rules seems to be in lvm2 package
** Package changed: udev (Ubuntu) => lvm2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995645
Title:
udevd: timeout: killing 'watershed sh -c
This bug affects me as well. I have this problem a lot when I work with
lvm commands. The process can't be killed and it takes up all my CPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995645
Title
This bug affects me to after adding some snapshots to my vg of virtual
machines.
My root vg doesn't contain any snapshots, just the vg that backs my
VM's.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
And still, a month and a half later, not even a triage of this bug.
I guess it might be time to move on to a new distro. Ubuntu seem like
they have better things to do than fix bugs that seem to continue on
from one release to another.
In any case, if I remove all of my LVM snapshots this proble
Not even a triage on this? This happens on *every* *single* boot, so I
have plenty of opportunity to provide additional debugging information
if needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995645
Title:
udevd:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995645
Title:
udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y''
To manage notifications about this bug go to:
http
13 matches
Mail list logo
