From: alessandro macuz <alessandro.macuz@gmail.com>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] " Failed to find physical volume <ZFS block device"
Date: Sun, 26 Sep 2021 16:22:17 +0200 [thread overview]
Message-ID: <CAFrGbuVR70RB8x=JYNK=qTtCc_UGnrhtXLNjDZuwai1MAF-eCg@mail.gmail.com> (raw)
In-Reply-To: <CAAMCDecFLoJ6ait9uUP0nQkYXZnMoPNre6v_1uBj=tGE_APtvg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2469 bytes --]
Thanks Roger, Zdenek,
I have my ZVOL on my NAS exposed as LUNs. The initiator were switched off
and for unknown reason I found my NAS switched off as well.
It had run for long and I feared the worst (CPU/motherboard/etc). Instead
once powered up everything started to work again but the LUNs that seemed
to jeopardized.
I have many ZVOLs used by ESXi in which I have EVE-NG who uses LVM and such
ZVOLs have the same size so I wanted to inspect them to check the hostname.
Now some LUNs started to work normally, some others still behave weirdly. I
will run pvs on them with extra debugs to see what's going on.
Many thanks,
Alex
Le jeu. 23 sept. 2021 à 23:48, Roger Heflin <rogerheflin@gmail.com> a
écrit :
> If you have lvmetad running and in use then the lvm commands ask it
> what the system has on it.
>
> I have seen on random boots fairly separated systems (rhel7 versions,
> and many years newer fedora systems) at random fail to find one or
> more pv.s
>
> I have disabled it at home, and in my day job we have also disabled
> (across 20k+ systems) as we confirmed it had inconsistency issues
> several times on a variety of our newest installs.
>
> Stopping lvmetad and/or restarting it would generally fix it. But
> it was a source of enough random issues(often failure to mount on a
> boot, so often issues that resulted in page-outs to debug) and did
> not speed things up much enough to be worth it even on devices with
> >2000 SAN volumes.
>
> On Thu, Sep 23, 2021 at 8:52 AM Zdenek Kabelac <zkabelac@redhat.com>
> wrote:
> >
> > Dne 22. 09. 21 v 18:48 alessandro macuz napsal(a):
> > > 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?
> > >
> > >
> >
> > Hi
> >
> > Yes - PVs do have header signature keeping information about PV
> attributes
> > and also has the storage area to keep lvm2 metadata.
> >
> > Partition flags known to fdisk are irrelevant.
> >
> >
> > Regards
> >
> > Zdenek
> >
> > _______________________________________________
> > 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/
> >
>
[-- Attachment #1.2: Type: text/html, Size: 3358 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-27 5:36 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
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 [this message]
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='CAFrGbuVR70RB8x=JYNK=qTtCc_UGnrhtXLNjDZuwai1MAF-eCg@mail.gmail.com' \
--to=alessandro.macuz@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=rogerheflin@gmail.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).