This happens frequently when attempting to create a snapshot: # lvcreate -s -L4G /dev/systemvg/edgy_chroot -n edgy-mongoose2 LV systemvg/edgy-mongoose2 in use: not deactivating Couldn't deactivate new snapshot.
And then evms_activate runs like crazy and then lvm following that, hammering my drives: root 15334 0.0 0.0 10304 648 ? S< 17:41 0:00 /lib/udev/watershed /sbin/evms_activate root 15335 0.0 0.0 10300 636 ? S< 17:41 0:00 /lib/udev/watershed /sbin/evms_activate root 15354 1.8 0.1 82364 4528 ? D<l 17:41 0:00 /sbin/evms_activate ...later... root 15416 0.0 0.0 10304 644 ? S< 17:41 0:00 /lib/udev/watershed /sbin/lvm vgck root 15418 0.0 0.0 13312 1576 ? D< 17:41 0:00 /sbin/lvm vgck root 15422 0.0 0.0 10304 640 ? S< 17:41 0:00 /lib/udev/watershed /sbin/lvm vgck I'm assuming some new race condition has been introduced. Also, it doesn't seem sensible to run vgck every time a lvm operation happens. This is pretty disk intensive. -- [feisty] failures when opening snapshots https://launchpad.net/bugs/84672 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
