All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian McCullough <bdmc@bdmcc-us.com>
To: Milan Broz <mbroz@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Missing PV
Date: Sat, 28 Apr 2012 13:01:35 -0400	[thread overview]
Message-ID: <20120428170135.GC1076@bdmcc-us.com> (raw)
In-Reply-To: <20120427030806.GB2819@bdmcc-us.com>


Milan,

I promised you an explanation, and here it is.


It was, at least partially, my fault.


I don't really understand why the original VM did not, and would not,
restart correctly.


However, I discovered, after I had made copies of everything and created
a new VM to work with, that there were two different "formats" of
"virtual disk drives," even though they were all called "qcow2."  There
were a combination of "raw" and "qcow2" disks.


Once I got the VM configuration file, and therefore the VM
configuration, matching the formats of the disk drives, I was able to
completely recover the "missing" PV, and therefore the VG and LV.

During my investigation, I had issued a "removemissing," so the LVM
Meta-data was "corrupted," but I edited a copy of that and 
vgcfgrestore corrected everything.


I did an e2fsck of the LV, to make sure, but the user tells me that
everything looks the way that he expected, so far.


So, even though the problem really wasn't what I thought it was, I want
to thank you very much for the patience and guidance toward helping me
find the ( apparent ) real problem.  

I am still not happy about how rebooting the host machine caused so much
damage, with one LV completely losing its contents ( the qcow2 file has
completely disappeared ) and therefore one VM being destroyed, and more
than this one not being able to restart correctly, but at least, most of
the VMs are back in action.


Thanks again,
Brian

      reply	other threads:[~2012-04-28 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 13:24 [linux-lvm] Missing PV Brian McCullough
2012-04-26 14:58 ` Brian McCullough
2012-04-26 16:47   ` Milan Broz
2012-04-26 17:23     ` Brian McCullough
2012-04-26 17:47       ` Milan Broz
2012-04-26 18:24         ` Brian McCullough
2012-04-26 19:43         ` Brian McCullough
2012-04-26 20:45           ` Milan Broz
2012-04-26 21:13             ` Brian McCullough
2012-04-27  3:08               ` Brian McCullough
2012-04-28 17:01                 ` Brian McCullough [this message]

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=20120428170135.GC1076@bdmcc-us.com \
    --to=bdmc@bdmcc-us.com \
    --cc=linux-lvm@redhat.com \
    --cc=mbroz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.