* [linux-lvm] VG metadata and snapshots
@ 2018-09-24 12:14 Henrik Johansson
0 siblings, 0 replies; only message in thread
From: Henrik Johansson @ 2018-09-24 12:14 UTC (permalink / raw)
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-09-24 12:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-24 12:14 [linux-lvm] VG metadata and snapshots Henrik Johansson
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).