From: Henrik Johansson <henrikj@henkis.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] VG metadata and snapshots
Date: Mon, 24 Sep 2018 14:14:51 +0200 [thread overview]
Message-ID: <758508B7-CC22-4D43-B83F-A2005D88686A@henkis.net> (raw)
Hello,
I have experienced something unexpected with one of our virtualised hosts. The VG containing root had been expanded to a secondary disk which contained /opt but no extents of the root filsystem. This host had some problems and was restored/cloned from an older snapshot, but only the first disk was overwritten leaving data on the expanded disk intact. Now it seems like LVM have started using the metadata configuration from the old disk, making both disks part of the VG without my intervention. Is this even possible, or is something at play here which I do not understand?
All disks are the same, same UUID and everything, but can a system boot and begin to this leftover metadata without any recovery? Should I not get something like “inconsistent metadata” and a failed boot?
Regards
Henrik
reply other threads:[~2018-09-24 12:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=758508B7-CC22-4D43-B83F-A2005D88686A@henkis.net \
--to=henrikj@henkis.net \
--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).