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't actually inform about them in a very meaningful way.
For example: Feb 12 12:39:57 hostname lvm[3325]: Logical volume lvname successfully resized Feb 12 12:39:59 hostname lvm[3325]: No longer monitoring snapshot vgname-lvname Feb 12 12:40:00 hostname lvm[3325]: dm_task_run failed, errno = 22, Invalid argument Here it did the extend but the next iteration didn't win the race and just silently dropped the ball afterwards...? Feb 12 12:44:39 hostname lvm[3325]: Snapshot vgname-lvname is now 92% full. Feb 12 12:44:40 hostname lvm[3325]: device-mapper: waitevent ioctl on failed: Interrupted system call Feb 12 12:44:40 hostname lvm[3325]: device-mapper: waitevent ioctl on failed: Interrupted system call Feb 12 12:44:44 hostname lvm[3325]: Extending logical volume lvname to 252.00 MiB Feb 12 12:44:44 hostname lvm[3325]: Monitoring snapshot vgname-lvname Feb 12 12:44:44 hostname lvm[3325]: Logical volume lvname successfully resized Feb 12 12:44:46 hostname lvm[3325]: No longer monitoring snapshot vgname-lvname Here it looked like it was winning the race but inbetween it noticing it should extend and actually extending, it actually lost the race, and then the last message came with a larger lag...? So it does appear that the original issue is fixed with the latest trusty packages, with non-trivial caveats. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424114 Title: lvm snapshot is not being autoextended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1424114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
