From: alessandro macuz <alessandro.macuz@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] " Failed to find physical volume <ZFS block device"
Date: Wed, 22 Sep 2021 18:48:23 +0200 [thread overview]
Message-ID: <CAFrGbuWKxbB=2Q6QygfN5mLh1MU7ztwXOouiRF2ynP-BcjhfXA@mail.gmail.com> (raw)
In-Reply-To: <CAFrGbuU63mCLDc47aiY6PuEf4C1B=CL3Dh1=GB+p_rRWkV8S4g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1529 bytes --]
fdisk correctly identifies the extended partition as 8e.
I wonder which kind of data lvmdiskscan and pvs use in order to list LVM
physical volumes.
Does PVS check some specific metadata within the partition without just
relying on the type of partition displayed by fdisk?
Alex
Le mer. 22 sept. 2021 à 01:36, alessandro macuz <alessandro.macuz@gmail.com>
a écrit :
> Hi all,
>
> I sought the web for the error " Failed to find physical volume
> "/dev/zd96p5"." but the closest discussion in the LVM archives I found
> was one of mine back in 2014
>
> https://listman.redhat.com/archives/linux-lvm/2014-June/msg00016.html
>
> This time though it seems pvs fails to find the physical volume when
> lvmdiskscan does recognize it. Do I have to really upgrade lvm2 or is there
> another way to have pvs recognize the volume?
>
> root@server:/etc# lvm version
> LVM version: 2.02.133(2) (2015-10-30)
> Library version: 1.02.110 (2015-10-30)
> Driver version: 4.34.0
> root@ server :/etc# lvmdiskscan -l
> WARNING: only considering LVM devices
> /dev/sda5 [ 74.05 GiB] LVM physical volume
> /dev/zd304p3 [ 19.00 GiB] LVM physical volume
> /dev/zd96p5 [ 1023.52 GiB] LVM physical volume
> * /dev/zd112p5 [ 1023.52 GiB] LVM physical volume*
> 0 LVM physical volume whole disks
> 4 LVM physical volumes
> root@ server :/etc# pvs -a /dev/zd96p5
> Failed to find physical volume "/dev/zd96p5".
>
> Thanks, Alex.
>
[-- Attachment #1.2: Type: text/html, Size: 2670 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2021-09-23 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 23:36 [linux-lvm] " Failed to find physical volume <ZFS block device" alessandro macuz
2021-09-22 16:48 ` alessandro macuz [this message]
2021-09-23 13:51 ` Zdenek Kabelac
2021-09-23 18:03 ` alessandro macuz
2021-09-23 18:43 ` Zdenek Kabelac
2021-09-23 21:48 ` Roger Heflin
2021-09-26 14:22 ` alessandro macuz
2021-09-28 18:47 ` Roger Heflin
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='CAFrGbuWKxbB=2Q6QygfN5mLh1MU7ztwXOouiRF2ynP-BcjhfXA@mail.gmail.com' \
--to=alessandro.macuz@gmail.com \
--cc=linux-lvm@redhat.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).