All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Harvell <joe.harvell@tekcomms.com>
To: linux-lvm@redhat.com
Cc: matthew patton <pattonme@yahoo.com>
Subject: Re: [linux-lvm] pvs complains of missing PVs that are not missing
Date: Thu, 10 Oct 2013 10:04:10 -0500	[thread overview]
Message-ID: <5256C1EA.8080805@tekcomms.com> (raw)
In-Reply-To: <1381361455.80237.YahooMailNeo@web181502.mail.ne1.yahoo.com>

Le 09/10/2013 18:30, matthew patton a �crit :
>> So I should set 'obtain_device_list_from_udev' to 0, then pvscan, vgscan
>> and lvscan?
>
> worth a shot. have you confirmed that udev has all the basic disk devices created?
>
I tried that to no avail.  Yes, all the block devices were present in 
/dev, both for the raw partitions and the RAID ones.

Does anyone know the algorithm LVM uses to determine whether PVs are 
present?  Also, I'd really like an LVM tool that reads the PV label off 
of a PV and displays it...I want to see what UUID label is actually on 
each PV.

  parent reply	other threads:[~2013-10-10 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 21:29 [linux-lvm] pvs complains of missing PVs that are not missing Joe Harvell
2013-10-09 21:49 ` Joe Harvell
     [not found] ` <1381356552.67129.YahooMailNeo@web181504.mail.ne1.yahoo.com>
2013-10-09 23:04   ` Joe Harvell
     [not found]   ` <5255D815.1090704@tekcomms.com>
     [not found]     ` <1381361455.80237.YahooMailNeo@web181502.mail.ne1.yahoo.com>
2013-10-10 15:04       ` Joe Harvell [this message]
2013-10-10 18:38         ` Peter Rajnoha
2013-10-10 18:48           ` Peter Rajnoha
2013-10-10 19:48           ` Joe Harvell
  -- strict thread matches above, loose matches on Subject: below --
2013-10-23  4:26 Shi Jin
2013-10-23 16:43 ` Joe Harvell
2013-10-24  9:35   ` Zdenek Kabelac
2013-10-24 15:30     ` Joe Harvell
2013-10-24 16:26       ` Alasdair G Kergon

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=5256C1EA.8080805@tekcomms.com \
    --to=joe.harvell@tekcomms.com \
    --cc=linux-lvm@redhat.com \
    --cc=pattonme@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.