*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213
** This bug is no longer a duplicate of bug 995645
udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y''
** This bug has been marked a duplicate of bug 1396213
LVM VG i
*** This bug is a duplicate of bug 995645 ***
https://bugs.launchpad.net/bugs/995645
It has the symptom of both bugs, 1. a lvm root volume with snapshot that
doesn't boot the OS, and 2. at boot time it stalls, show "timeout:
killing 'watershed... lvm vgscan..." and drop to shell. After I remov
*** This bug is a duplicate of bug 995645 ***
https://bugs.launchpad.net/bugs/995645
On Fri, Apr 11, 2014 at 06:55:15PM -, Seth wrote:
> I'd like to have the record show that this bug is ancient so we can
> measure the level of neglect.
Snapshot loading got speeded up in upstream kernel
*** This bug is a duplicate of bug 995645 ***
https://bugs.launchpad.net/bugs/995645
@Anderson The fact that "it's happening here" doesn't make this a dupe.
In fact, it makes /that/ a dupe of this one, ~3 years OLDER.
I'd like to have the record show that this bug is ancient so we can
measure
*** This bug is a duplicate of bug 995645 ***
https://bugs.launchpad.net/bugs/995645
A lvm root volume snapshot that has many changes takes too long to activate
(lvchange -ay volume). At boot time it doesnt wait and kill process "watershed
sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'",
*** This bug is a duplicate of bug 995645 ***
https://bugs.launchpad.net/bugs/995645
@Anderson Luiz Alves: Are you sure this bug is an exact duplicate of
#995645?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 995645 ***
https://bugs.launchpad.net/bugs/995645
** This bug has been marked a duplicate of bug 995645
udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y''
--
You received this bug notification because you are a member
Forgot about the problem when I upgraded to Precise 12.04 from oneiric.
I have root on lvm and I took a snapshot before upgrade. Everthing
worked fine for couple of boots and after _one_ day of using the machine
My system timedout on watersched vgchange -a y, but the lvm volume was
availeble in ini
I just reproduced this on a remote server, I had a "natty" snapshot (am now on
11.10). After deleting the snapshot system booted just fine. This effectively
kills the snapshot function for the rootfs.
Took me a few hours to get a remote console and figure this one out.
--
You received this bug
Metadata (not data) is cached i.e. the block mappings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360237
Title:
cannot boot root on lvm2 with (largish) snapshot
To manage notifications about this
Persistent on disk, but cached completely in memory by reading the entire COW
device when activating it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360237
Title:
cannot boot root on lvm2 with (la
On 01/07/2012 08:08 PM, Ray Van Dolson wrote:
> I believe this is normal behavior for LVM. LVM has to build an overlay
> layer from all of the blocks contained in the snapshot so they are
> available via access to the "parent" LV at any time.
>
> The larger the snapshot, the longer it takes to rea
I believe this is normal behavior for LVM. LVM has to build an overlay
layer from all of the blocks contained in the snapshot so they are
available via access to the "parent" LV at any time.
The larger the snapshot, the longer it takes to read in all of the
blocks and build the overlay layer.
--
I'm experiencing the same thing. With a full snapshot and a disabled
splash screen, I get an error message telling me that a command has
timeouted (lvscan, IIRC), and it had been terminated. I removed the
snapshot and it booted all right.
I think terminating boot commands using a predefined timeou
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (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/360237
Title:
cannot
I've run into this still with Ubuntu 10.04. The issue is exactly as
described, where lvchange -a y takes significant time to run, causing
the boot to fail. In my case, I had a 200G allocated snapshot against a
2TB LV, with about 40% in use.
--
You received this bug notification because you are a
I've seen this exact behavior on two different sets of hardware. Both
running LVM on top of RAID-1. I've seen it happen in both intrepid and
jaunty
--
cannot boot root on lvm2 with (largish) snapshot
https://bugs.launchpad.net/bugs/360237
You received this bug notification because you are a membe
Ubuntu bugs should generally be filed on the appropriate package in
Ubuntu rather than on the upstream project. Moving the bug to Ubuntu's
lvm2 package.
** Also affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lvm2
Status: New => Invalid
--
cannot boot ro
18 matches
Mail list logo
