From: Ray Morris <support@bettercgi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Recovering Accidentally Destroyed LVM2 Information
Date: Wed, 27 Apr 2011 09:57:28 -0500 [thread overview]
Message-ID: <20110427095728.6317526d@bettercgi.com> (raw)
In-Reply-To: <BANLkTinZzxt2c01=uN6VUXVHFsbXK2Mm6A@mail.gmail.com>
vgcfgrestore -f /etc/lvm/archive/FILENAME VGNAME
But see "man vgcfgrestore"
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On Tue, 26 Apr 2011 20:58:25 -0700
Chris Streeter <chris@chrisstreeter.com> wrote:
> > What you *should* have done is restore the metadata to the point
> > before your errant command. Â You can still do that (if it is still
> > in the archive), but the several K of zeros written to the start of
> > the LV you created will require recovery.
>
> So I still have all the files in the archive of the form
> raid_vg_0000*.vg
>
> If have those files, how would I go about restoring the metadata to
> the device? If I were to loose several K of data, I'm totally fine
> with that.
>
> Thanks!
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2011-04-27 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 3:12 [linux-lvm] Recovering Accidentally Destroyed LVM2 Information Chris Streeter
2011-04-27 3:41 ` Stuart D. Gathman
2011-04-27 3:58 ` Chris Streeter
2011-04-27 13:03 ` Stuart D. Gathman
2011-04-27 14:57 ` Ray Morris [this message]
2011-04-27 22:02 ` Chris Streeter
-- strict thread matches above, loose matches on Subject: below --
2011-04-27 3:07 Chris Streeter
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=20110427095728.6317526d@bettercgi.com \
--to=support@bettercgi.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).