From: Heinz Mauelshagen <Mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Lost free PV -> error reading VG
Date: Fri Feb 20 10:35:06 2004 [thread overview]
Message-ID: <20040220153630.GD25086@redhat.com> (raw)
In-Reply-To: <4034F7F3.2040006@demonlord.de>
Christian,
never "rm -r /etc/lvm*" !!!
o vgscan deletes and creates /etc/lvmtab and volume group
backup files in /etc/lvmtab.d/ new
o /etc/lvmconf/ archive files get updated by _any_ configuration changing
command or by explicitely running vgcfgbackup
Of course you might want to remove certain archive files from /etc/lvmconf/
after many configuration changes because archives of removed VGs don't get
deleted automatically for obvious reasons.
But yuu *never* *ever* want to do that without having an actual backup
of /etc/lvmconf/*.
FYI: LVM2 keeps metadata backups and archives uin different locations
(see /etc/lvm/lvm.conf there)
Regards,
Heinz -- The LVM Guy --
On Thu, Feb 19, 2004 at 06:52:51PM +0100, Christian Reiss wrote:
> Heinz Mauelshagen wrote:
>
> >
> >/me wonders how often we mentioned to take backups of /etc/lvmconf/* yet
> >:->
> >
>
> From a Users point of view:
> If you run vgscan, and it even mentions something about
>
> a) REBuilding /etc/lvmwhatever
> and
> b) it fails for *any* reason,
>
> people, me included, delete /etc/lvm* to start "clean",
> and give vgscan the opportunity to start fresh, without
> any "corrupted" data.
>
> I dont know how often I nuked the backups, even after i
> knew that deleting /etc/lvm* is not a good idea. Its like
> a reflex.
>
> -Christian
>
>
>
>
> --
> Christian Reiss <email@demonlord.de>
> demonserver.de
>
> Key fingerprint = 2999 B7CD A218 06DF D658 5BE3 18B6 B232 02FF 71B2
> Public Key can be obtained here: http://www.demonlord.de/pgp.txt
>
> _______________________________________________
> 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/
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-02-20 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 11:07 [linux-lvm] Lost free PV -> error reading VG Stefan Jenkner
2004-02-19 10:39 ` Heinz Mauelshagen
2004-02-19 12:51 ` Christian Reiss
2004-02-20 10:35 ` Heinz Mauelshagen [this message]
2004-02-20 3:20 ` Stefan Jenkner
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=20040220153630.GD25086@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 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.