From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgscan vs vgcfgrestore
Date: Mon, 23 Aug 2004 15:42:53 +0200 [thread overview]
Message-ID: <20040823134253.GB9740@redhat.com> (raw)
In-Reply-To: <025001c484ce$95942560$5208580a@b034547>
On Tue, Aug 17, 2004 at 10:53:48PM -0400, Rob Schwartz wrote:
> Hello Heinz,
>
> Forgive me for writing in English. As I come from the United States I am embarassingly uni-lingual. I have been working with LVM for several months now and finally have had the opportunity to get into the guts of the lvm configuration. I am preparing myself for the situation where my LVM environment gets corrupted in some manner. Actually, last week I encountered a problem with LVM and was unable to quickly recover so I ended up simply rebuilding the LVM PV's, VG's and LV's and restoring data. Fortunately, it was an easy restore. I have been comparing the vgscan utility with vgcfgrestore. In a test environment I have deleted the /etc/lvm* stuff and even deleted the /dev/lvm* stuff and successfully recovered the VG and LV by simply doing a vgscan.
Yes, vgscan's task is to discover any PVs, retrieve the LVM metadata, store
it in /etc/lvmtab* and created devnodes for access to the VGs/LVs.
> Whew... nice... I understand vgcfgbackup and vgcfgrestore but am not sure when I would need to use the configuration backup. The VGDA as I understand it is stored on the PV's. If I have the PV's intact I therefore have the VGDA and hence am able to recover using vgscan. When would I need to use vgcfgrestore?
You indirectly answered your onw question ;)
You need vgcfgrestor, when the metadata on the PVs is *not* intact (eg,
accidential overwrite or starnge crash). and vgscan fails to discover
your VG(s).
> I have found much information on LVM on the web but nothing that really pinpoints my question. If there is something out there that I can refer to, please tell me.
Have you referenced the LVM-HOWTO yet (URL below) ?
>
> Regards,
> Rob
> _______________________________________________
> 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/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2004-08-23 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 2:53 [linux-lvm] vgscan vs vgcfgrestore Rob Schwartz
2004-08-23 13:42 ` Heinz Mauelshagen [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=20040823134253.GB9740@redhat.com \
--to=mauelshagen@redhat.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