linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Eric Ren <zren@suse.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] When and why vgs command can change metadata and incur old metadata to be backed up?
Date: Mon, 30 Oct 2017 14:06:45 +0800	[thread overview]
Message-ID: <a118652b-470d-0524-7a6a-109fea394895@suse.com> (raw)

Hi all,

Sometimes, I see the following message in the VG metadata backups under 
/etc/lvm/archive:

"""
contents = "Text Format Volume Group"
version = 1

description = "Created *before* executing 'vgs'"
"""

I'm wondering when and why the new backups will be created by reporting 
command like vgs?

Thanks in advance!
Eric

             reply	other threads:[~2017-10-30  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  6:06 Eric Ren [this message]
2017-10-30 17:04 ` [linux-lvm] When and why vgs command can change metadata and incur old metadata to be backed up? David Teigland
2017-10-30 18:11   ` Gionatan Danti
2017-10-30 18:50     ` David Teigland
2017-10-31  7:54     ` Eric Ren
2017-10-30 22:56 ` Alasdair G Kergon
2017-11-04  7:24   ` Eric Ren

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=a118652b-470d-0524-7a6a-109fea394895@suse.com \
    --to=zren@suse.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).