I did some more testing with that trusty system and it does appear to be
working much better than before (i.e. not at all), though it seems there
are obfuscating circumstances - AFAICT it looks like it recognizes lost
causes (100.00% full snapshots) that it then no longer tries to extend,
but doesn
@Donk yes, of course.
% ps auxfw | grep '[d]'meventd
root 3325 0.1 0.0 574972 18956 ?Shttps://bugs.launchpad.net/bugs/1424114
Title:
lvm snapshot is not being autoextended
Status in lvm2 package in Ubuntu:
Confirmed
Bug description:
After setting auto extend threshold and r
It looks like it works on Ubuntu 16, syslog contains things like:
Feb 10 11:28:55 hostname lvm[1704]: WARNING: Snapshot vgname-lvname is now
80.03% full.
Feb 10 11:28:55 hostname lvm[1704]: Size of logical volume vgname/lvname
changed from 1.00 GiB (256 extents) to 1.20 GiB (308 extents).
Feb 10
On Ubuntu 14, it doesn't seem to work with monitoring = 1 set, either. I
had also tried doing vgchange --monitor y --poll y volumegroup, and
lvcreate --snapshot --monitor y ... and there was no effect.
Testing on Ubuntu 16 now
--
You received this bug notification because you are a member of Ubu
I also see this race condition happen often when I open up and
manipulate nested LVM devices.
For example, an LV is partitioned and one of the partitions inside is a
PV. A kpartx -a is run to activate the partitions, vgimportclone is run
to rename the VG inside that nested PV, and as MatthewParslo
5 matches
Mail list logo
