All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Schöftner" <rmu@unfoo.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] harddisk dies while pvmove is in progress
Date: Tue, 13 Sep 2011 00:15:18 +0200	[thread overview]
Message-ID: <4E6E8476.6030609@unfoo.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1109121706310.19095@bmsred.bmsi.com>

On 2011-09-12 23:08, Stuart D. Gathman wrote:
> On Mon, 12 Sep 2011, Robert Sch?ftner wrote:
>
>> So, LV homevideo is definitely lost, but shares seems to be OK, 
>> modulo the "running"/interrupted pvmove. Is there a way to clean up 
>> this mess without creating another LV and copying the contents of 
>> shares over?
>
> Remove the missing PV as the error message suggested.  Unless you
> have some hope of resurrecting it (has had success with connecting
> deceased drive via USB and putting in freezer to run it long enough
> to recover a little more data), it is gone now.
there is no hope in resurrecting the drive. it spins up, but doesn't 
show up, neither via direct sata connection nor via sata - usb bridge. 
and i already sent it away for warranty replacement.

my interpretation of the man page is that vgreduce --removemissing 
--force would remove both LVs, even the "good" one, that's what i want 
to avoid. my idea would be something like manually breaking the mirror 
from the raid to the missing harddisk, at least for the part that 
belongs to the LV "shares".

my plan is to edit the latest archived meta-data, remove the 
pvmove-mirror, exchange the segment pointing to the missing device with 
the mirrored segment, and vcfgrestore it, if no better idea comes up. 
the saved metadata confirms that the segment belonging to LV "shares" 
was completely mirrored before the harddisk died, so all the needed data 
is there.

thx
Robert

  reply	other threads:[~2011-09-12 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 20:30 [linux-lvm] harddisk dies while pvmove is in progress Robert Schöftner
2011-09-12 21:08 ` Stuart D. Gathman
2011-09-12 22:15   ` Robert Schöftner [this message]
2011-09-14  7:23     ` Robert Schöftner
2011-09-14 16:55       ` Ray Morris
2011-09-14 17:25       ` Stuart D. Gathman

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=4E6E8476.6030609@unfoo.net \
    --to=rmu@unfoo.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 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.