linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Damon Wang <damon.devops@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Wyllys Ingersoll <wyllys.ingersoll@keepertech.com>
Subject: Re: [linux-lvm] Device XXX excluded by a filter - why??
Date: Thu, 31 May 2018 10:17:49 +0800	[thread overview]
Message-ID: <CABZYMH5q5ciYi6fEc7OW_XVwtBWXEy3K+ibMTnyTnaWbW9-qzw@mail.gmail.com> (raw)
In-Reply-To: <c853a9c2-14e1-d4eb-d6a9-7bc90fb9bcfc@redhat.com>

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/

      reply	other threads:[~2018-05-31  2:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 15:53 [linux-lvm] Device XXX excluded by a filter - why?? Wyllys Ingersoll
2018-05-30 10:49 ` Marian Csontos
2018-05-31  2:17   ` Damon Wang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABZYMH5q5ciYi6fEc7OW_XVwtBWXEy3K+ibMTnyTnaWbW9-qzw@mail.gmail.com \
    --to=damon.devops@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=wyllys.ingersoll@keepertech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).