Could you please file a new bug against LVM/lucid (just add a tag 'lucid') detailing this behavior? Thanks.
I've never been a fan of LVM's filtering mechanism, then again the source is there, I could do something about it :) What you described here: """ However as soon as I use something like: filter = [ "a|.*|", "r|loop[0-9]|" ] Then I don't get any filtering at all... except that defining _only_ the removal filters, per: filter = [ "r|loop[0-9]+|" ] .. and other filters of that ilk DO work as expected -- so long as I remove the "accept-all" regex. """ Sounds like a bug to me. The whole point of this filter-in, filter-out mechanism is to perform operations that exclude everything by default, and then allow only certain devices in. Just like you would configure a firewall. As for multipath aliasing, it happens more often than I would like, which is why I made such a point to include it into the official documentation. Once you start stacking block devices it can get complicated very quickly. We should probably expand the docs to include udev alias examples, as configurations like yours are the second most common e.g. disk 1 not part of VG but everything else is. Glad we could get you sorted. I really appreciate the level of detail and responsiveness you were able to provide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020436 Title: Cannot read superblock after FC multipath failover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
