linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Brian McCullough <bdmc@bdmcc-us.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Missing PV
Date: Thu, 26 Apr 2012 19:47:24 +0200	[thread overview]
Message-ID: <4F998A2C.6030909@redhat.com> (raw)
In-Reply-To: <20120426172338.GA1355@bdmcc-us.com>

On 04/26/2012 07:23 PM, Brian McCullough wrote:

>> You said you have missing PV, right?
> 
> In the case of the machine in question, the original "disk" was found to
> be too small by the user, and another qcow file was created to handle
> the excess.
> 
> Last Tuesday ( a week+ ago ), the primary Sysadmin for the host machine
> rebooted the machine for various reasons, I understand, and afterward
> this VM would not restart, with a missing PV.
> 
> 
> 
>> - why the PV is missing? What exactly happened?
>> (overwritten, removed from system, hw failed?)
> 
> The qcow file is still there, but LVM claims that it is missing, from
> what I understand from the messages.

Are you sure that VM see that second qcow file content? I don't think so.

It seems lvm is not your problem at all. I guess once you fix your
VM configuration lvm will activate that without any data lost.

Or is that qcow file corrupted?

Check with lsblk (if available) and /dev/ that you _really_ physical
device which was added later. If not, the question is what
changed in your VM that after reboot it is not visible?

Check log when starting VM - it must log that second qcow is used.
Check log inside guest - which device were there (/dev/vdc?) and
now missing... etc

> unknown device eyeball  lvm2 a-   40.00g 20.00g kXXFhn-oalZ-9D12-0CvG-6b4w-RjcE-Jb171k

>   LV     VG      Attr   LSize   Origin Snap%  Move Log Copy%  Convert Devices          
> home   eyeball -wi---  89.89g /dev/vdb2(2268)  
> home   eyeball -wi---  89.89g unknown device(0)

From this I guess 20GB of data missing on the end of home. quite a lot...

>> All recovery now depends on info above and what you really want:
>>
>> 1) either you have old disk and you want to recover metadata on it
>> and attach it back to VG
>>
>> 2) or you want just recover data from existing PVs
>> (replace missing PV segments with zeroes for example)
>>
>> 3) or you want completely remove all LVs which were even partially on this
>> lost PV (no data recovery, just make VG consistent again)
>>
>> What is the option you want to do? I guess 2) ?
> 
> You are correct.  Number 2 is my goal.

With the info above I think you should try 1) first :)

Milan

  reply	other threads:[~2012-04-26 17:47 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 [this message]
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

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=4F998A2C.6030909@redhat.com \
    --to=mbroz@redhat.com \
    --cc=bdmc@bdmcc-us.com \
    --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).