On Mon, 2009-02-23 at 17:44 +0000, Alasdair G. Kergon wrote: > It's also worth trying it without any vgscans at all - it ought to > cope without nowadays provided all commands access VGs by name > i.e. 'vgchange -ay vg1' and never 'vgchange -ay'. > It'll trigger a vgscan internally if it can't find a VG that > was explicitly named. > Which will cause the exact same problem we're seeing :-/
Scott -- Scott James Remnant sc...@canonical.com -- udev repeatedly generates "change" events for the same block device(s) https://bugs.launchpad.net/bugs/332270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
