linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: giuseppe@vacanti.org,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] PV not found
Date: Sat, 15 Dec 2018 21:04:54 -0500	[thread overview]
Message-ID: <23573.45766.916661.546759@quad.stoffel.home> (raw)
In-Reply-To: <167b30557b8.d471a29712958.970233558882873666@vacanti.org>


Giuseppe> after a reboot after a maintenance power interruption of a
Giuseppe> few hours, one of my LVs is not coming back (Ubuntu
Giuseppe> 18.04). The situation I am at is the following:

Ouch, this isn't fun.  

Giuseppe> - the physical disk is an iSCSI and it is seen by the kernel as /dev/sdc

Does it have any partitions on it?  Is this the only iSCSI volume on
the system?  

Giuseppe> - lvmdiskscan -v sees the PV on /dev/sdc
Giuseppe>   /dev/sdc              [      72.76 TiB] LVM physical volume

Can you show the full details of all your LVMs please?  Do any of the
others have a conflict with this device?

Giuseppe> - blkid returns the UUID that I can also find in the LVM configuration
Giuseppe>  /dev/sdc: UUID="fvUXXf-pVOF-EPnn-c8eg-tZ5S-iMVW-wsSFDy" TYPE="LVM2_member"

That's good.  What about if you do:

       pvchange -v /dev/sdc

what happens then?  

Giuseppe> - this entry lacks a PARTUUID entry that other LVs on the
Giuseppe> system have. Is this a clue? I could not quite connect this
Giuseppe> piece of info with anything.

Can you show the full output and the differences?

Giuseppe> - pvscan does not report /dev/sdc

Not good.

Giuseppe> - pvdisplay does not seem to know about this PV
Giuseppe>   pvdisplay /dev/sdc
Giuseppe>   Failed to find physical volume "/dev/sdc"

Not good either. How about the 'pvchange' and/or 'vgchange -ay' as
well?  Maybe the iSCSI LUN is getting mapped after all the rest of the
LVM setup happens...

Giuseppe> Reading man pages and searching the web does not really
Giuseppe> bring me closer to understanding what is happening. This
Giuseppe> machine has its OS on LVs and those have all come back, and
Giuseppe> of course it is not the first time that I reboot. Probably I
Giuseppe> lack the correct terms to describe the problem so that I can
Giuseppe> find a solution. Anybody here on this list who can point me
Giuseppe> in the right direction?

By any chance did you put a partition table on there?  What system is
the iSCSI LUN being exported from?  Can you run the following iscsiadm
command and share the details?

 iscsiadm --mode discoverydb --type sendtargets --portal <IP> --discover

where <IP> is the address of the iSCSI server you're mounting from.
Did that server go down as well?

Good luck!
John

  reply	other threads:[~2018-12-16  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 17:59 [linux-lvm] PV not found Giuseppe Vacanti
2018-12-16  2:04 ` John Stoffel [this message]
2018-12-16  7:47   ` Giuseppe Vacanti
2018-12-16 20:40 ` Gionatan Danti
2018-12-17 20:41   ` Giuseppe Vacanti
2019-01-02 15:23     ` 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=23573.45766.916661.546759@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=giuseppe@vacanti.org \
    --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).