All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Gathman <stuart@gathman.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM issues after replacing linux mdadm RAID5 drive
Date: Fri, 02 May 2014 00:02:25 -0400	[thread overview]
Message-ID: <536318D1.7050809@gathman.org> (raw)
In-Reply-To: <20140426204744.25b201e4@netstation>

Long ago, Nostradamus foresaw that on 04/26/2014 02:47 PM, L.M.J would
write:
>
> I presume I still have data on my broken RAID5.
>
> I did a pvcreate --restorefile and vgcfgrestore.
Did you restore the raid 5, taking out the new drive, and add00ing it
back in properly?  I can't take the time right now to give you a step by
step.  The big warning on what you did wasn't a joke.  You should get
help from md driver people.  You do not have an LVM problem.

> I can see now my 2 LVM, but my EXT4 filesystem are empty, df reports
some realist disk usage, fsck (Read only) find ? tons of errors. Is
there a way to recover my data on the EXT4 FS ? Le Fri, 18 Apr 2014
23:14:17 +0200, "L.M.J"

None of that is relevant until you restore your raid 5.  Your problem
was that you told md that your new blank drive was good, in-sync data. 
Which is obviously isn't.  You need to degrade your raid back to the one
missing drive.  Then add the new drive normally - NOT using that experts
only shortcut with the big warning, which you used incorrectly.

  parent reply	other threads:[~2014-05-02  4:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 10:23 [linux-lvm] LVM issues after replacing linux mdadm RAID5 drive L.M.J
2014-04-17 19:33 ` Stuart Gathman
2014-04-18 21:14   ` L.M.J
2014-04-26 18:47     ` L.M.J
2014-04-30 20:57       ` L. M. J
2014-05-02  4:02       ` Stuart Gathman [this message]
2014-05-04  7:57         ` L.M.J

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=536318D1.7050809@gathman.org \
    --to=stuart@gathman.org \
    --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.