From: "Rob Schwartz" <rschwartz@boscovs.com>
To: Linux-LVM@Sistina.com
Subject: [linux-lvm] vgscan vs vgcfgrestore
Date: Tue, 17 Aug 2004 22:53:48 -0400 [thread overview]
Message-ID: <025001c484ce$95942560$5208580a@b034547> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
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. 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? 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.
Regards,
Rob
[-- Attachment #2: Type: text/html, Size: 1922 bytes --]
next reply other threads:[~2004-08-18 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 2:53 Rob Schwartz [this message]
2004-08-23 13:42 ` [linux-lvm] vgscan vs vgcfgrestore Heinz Mauelshagen
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='025001c484ce$95942560$5208580a@b034547' \
--to=rschwartz@boscovs.com \
--cc=Linux-LVM@Sistina.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