[linux-lvm] Device XXX excluded by a filter - why??

[linux-lvm] Device XXX excluded by a filter - why??

[Wyllys Ingersoll]

Using the following lvm2 version on Ubuntu 16.04.3 running kernel 4.16.03
  LVM version:     2.02.176(2) (2017-11-03)
  Library version: 1.02.145 (2017-11-03)
  Driver version:  4.37.0

ceph-volume attempts to create a VG on a raw block device to use as a
bluestore OSD.  The command it uses looks like this:

vgcreate --force --yes ceph-a637b0e7-e54f-4fe9-8afc-a74671d94f6e /dev/sdi

The disk (/dev/sdi) in this case is a blank (no partition table) GPT
label 3.7T drive.

vgcreate complains and fails:
     stderr: Device /dev/sdi excluded by a filter.

I cannot figure out what "filter" is causing this.  The global_filter
in lvm.conf is wide open:
filter = [ "a|.*/|" ]

Turning up debug logging does not show any additional reasons.
Repeatedly running pvscan or vgscan to update the cache does not fix
it either.

What could be blocking this device from being used?

thanks,
   Wyllys Ingersoll
   Keeper Technology, LLC

Re: [linux-lvm] Device XXX excluded by a filter - why??

[Marian Csontos]

On 05/23/2018 05:53 PM, Wyllys Ingersoll wrote:
> Using the following lvm2 version on Ubuntu 16.04.3 running kernel 4.16.03
>    LVM version:     2.02.176(2) (2017-11-03)
>    Library version: 1.02.145 (2017-11-03)
>    Driver version:  4.37.0
> 
> ceph-volume attempts to create a VG on a raw block device to use as a
> bluestore OSD.  The command it uses looks like this:
> 
> vgcreate --force --yes ceph-a637b0e7-e54f-4fe9-8afc-a74671d94f6e /dev/sdi
> 
> The disk (/dev/sdi) in this case is a blank (no partition table) GPT
> label 3.7T drive.

So is it a GPT device or not? If yes, it HAS a partition table after 
all, and LVM filters such devices out, even if the partition table is empty.

Run `wipefs -a /dev/sdi` first to remove any FS/GPT signatures.

-- Martian
> 
> vgcreate complains and fails:
>       stderr: Device /dev/sdi excluded by a filter.
> 
> I cannot figure out what "filter" is causing this.  The global_filter
> in lvm.conf is wide open:
> filter = [ "a|.*/|" ]
> 
> Turning up debug logging does not show any additional reasons.
> Repeatedly running pvscan or vgscan to update the cache does not fix
> it either.
> 
> What could be blocking this device from being used?
> 
> thanks,
>     Wyllys Ingersoll
>     Keeper Technology, LLC
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

Re: [linux-lvm] Device XXX excluded by a filter - why??

[Damon Wang]

Some additional tips, you can use `partprobe -s /dev/sdi` or `wipefs
/dev/sdi` to find out whether some magic string(filesystem, gpt, etc)
on it.

And use lvmdiskscan to find all available disk on server.

Damon

2018-05-30 18:49 GMT+08:00 Marian Csontos <mcsontos@redhat.com>:
> On 05/23/2018 05:53 PM, Wyllys Ingersoll wrote:
>>
>> Using the following lvm2 version on Ubuntu 16.04.3 running kernel 4.16.03
>>    LVM version:     2.02.176(2) (2017-11-03)
>>    Library version: 1.02.145 (2017-11-03)
>>    Driver version:  4.37.0
>>
>> ceph-volume attempts to create a VG on a raw block device to use as a
>> bluestore OSD.  The command it uses looks like this:
>>
>> vgcreate --force --yes ceph-a637b0e7-e54f-4fe9-8afc-a74671d94f6e /dev/sdi
>>
>> The disk (/dev/sdi) in this case is a blank (no partition table) GPT
>> label 3.7T drive.
>
>
> So is it a GPT device or not? If yes, it HAS a partition table after all,
> and LVM filters such devices out, even if the partition table is empty.
>
> Run `wipefs -a /dev/sdi` first to remove any FS/GPT signatures.
>
> -- Martian
>
>>
>> vgcreate complains and fails:
>>       stderr: Device /dev/sdi excluded by a filter.
>>
>> I cannot figure out what "filter" is causing this.  The global_filter
>> in lvm.conf is wide open:
>> filter = [ "a|.*/|" ]
>>
>> Turning up debug logging does not show any additional reasons.
>> Repeatedly running pvscan or vgscan to update the cache does not fix
>> it either.
>>
>> What could be blocking this device from being used?
>>
>> thanks,
>>     Wyllys Ingersoll
>>     Keeper Technology, LLC
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/