From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Jewsco Pius Jacquez <JewscoPius.Jacquez@Amdocs.com>
Subject: Re: [linux-lvm] metadata copies
Date: Wed, 10 Aug 2011 22:04:36 +0200 [thread overview]
Message-ID: <4E42E454.7000902@redhat.com> (raw)
In-Reply-To: <883D98939E388E429EE8D771168A6560027EE6AE1D@USCMIMAIL1.corp.amdocs.com>
On 08/10/2011 06:30 PM, Jewsco Pius Jacquez wrote:
> If you have two metadata copies stored in one PV, how does the OS know which one is the legitimate copy?
Only one metadata copy is always active.
There is sequence ID (see seqno = X in metadata backup).
If there are several PVs and more versions of metadata present, the one with highest sequence ID
is used and other PVs are automatically updated to this version.
Every LVM operation which changes metadata also increases this sequence id.
Milan
next prev parent reply other threads:[~2011-08-10 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 16:30 [linux-lvm] metadata copies Jewsco Pius Jacquez
2011-08-10 20:04 ` Milan Broz [this message]
2011-08-10 21:00 ` Stuart D. Gathman
2011-08-11 9:11 ` Milan Broz
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=4E42E454.7000902@redhat.com \
--to=mbroz@redhat.com \
--cc=JewscoPius.Jacquez@Amdocs.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).