From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Why LVM metadata locations are not properly aligned
Date: Thu, 21 Apr 2016 11:11:53 +0100 [thread overview]
Message-ID: <20160421101153.GE11336@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAAYit8QQKv1gwtQ5TQx1+aX2f0y8jmTMDU83cMqp2Obosom=jQ@mail.gmail.com>
On Thu, Apr 21, 2016 at 12:08:55PM +0800, Ming-Hung Tsai wrote:
> However, it's hard to achieve that if the PV is busy running IO.
So flush your data in advance of running the snapshot commands so there is only
minimal data to sync during the snapshot process itself.
> The major overhead is LVM metadata IO.
Are you sure? That would be unusual. How many copies of the metadata have you
chosen to keep? (metadata/vgmetadatacopies) How big is this metadata? (E.g.
size of /etc/lvm/backup/<vgname> file.)
Alasdair
prev parent reply other threads:[~2016-04-21 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 4:08 [linux-lvm] Why LVM metadata locations are not properly aligned Ming-Hung Tsai
2016-04-21 9:54 ` Zdenek Kabelac
2016-04-21 13:22 ` Zdenek Kabelac
2016-04-22 8:43 ` Ming-Hung Tsai
2016-04-22 9:49 ` Zdenek Kabelac
2016-04-21 10:11 ` Alasdair G Kergon [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=20160421101153.GE11336@agk-dp.fab.redhat.com \
--to=agk@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;
as well as URLs for NNTP newsgroup(s).