From: Giuseppe Vacanti <giuseppe@vacanti.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] PV not found
Date: Mon, 17 Dec 2018 20:41:09 -0000 [thread overview]
Message-ID: <167bde59673.fc2fc0a351387.5941487526649049402@vacanti.org> (raw)
In-Reply-To: <807b41c03c2d66e16153a8ee3489b4f1@assyoma.it>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hello, I have found a solution to the problem, however the problem seems to come back after every reboot. I have been put on the good path by the remarks made on this list by John and Gionatan. The fix is the following: - convince myself that the device has the correct uuid, I used blkid and compared the result with the information in the lvm backup - run pvck -t on /dev/sdc. Nothing special, all seems OK - run vgscan --cache. This command brings back knowledge of the VG the PV belongs to - now pvs lists my PV again, but the LV is inactive - I activate the LV with lvchange - all is back, I can mount and use the LV After a reboot however the information about the VG is gone again, and I have to repeat the steps above to be able to use the LV. I have a running system, but I don't know what is happening. Where can I look to figure this out? Regards, Giuseppe -- Giuseppe Vacanti
[-- Attachment #2: Type: text/html, Size: 1580 bytes --]
next prev parent reply other threads:[~2018-12-17 20:41 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
2018-12-16 7:47 ` Giuseppe Vacanti
2018-12-16 20:40 ` Gionatan Danti
2018-12-17 20:41 ` Giuseppe Vacanti [this message]
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=167bde59673.fc2fc0a351387.5941487526649049402@vacanti.org \
--to=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).