<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 01/02/2018 03:03 AM, Marian Csontos wrote: </div> <blockquote type="cite" cite="mid:e70ef50c-08ed-b75b-df30-8eae007fa556@redhat.com">Filters accept any device if any of it's "names" (all symbolic links) is matched by an a pattern ("a|.*/|" in your case) and matches no previous r pattern</blockquote> I don't follow you. The name being processed in that log *does* match a previous r pattern. <blockquote type="cite" cite="mid:e70ef50c-08ed-b75b-df30-8eae007fa556@redhat.com">for example anything in /dev/mapper/ is accepted. </blockquote> Yes, I'd considered that might be an issue, but that's not the block device name that the logs indicate is being used. A path that I've specifically rejected is being processed. If a second path to the block device might be processed, then I can see the need to make additional changes, but I can't solve that problem without understanding the basic logic of the filter system. The documentation in lvm.conf says "The first regex in the list to match the path is used, producing the 'a' or 'r' result for the device." but that doesn't seem to be correct. </body> </html>