From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Slow response from lvs and vgs commands
Date: Wed, 28 Jan 2015 10:28:48 +0100 [thread overview]
Message-ID: <54C8ABD0.4090402@redhat.com> (raw)
In-Reply-To: <CAPcfVV-KGCWda4fKdtVdo=xGQftCU8kURoqR6PDuLKz15wpKqg@mail.gmail.com>
Dne 27.1.2015 v 16:04 Marcos Dutra napsal(a):
> Hi everybody,
>
> I have the same problem when I use vgs command, so I used vgs -vvv command and
> it was slow when the output command showed me this "Archiving volume group
> "vgoracle" metadata (seqno 3)", I have many vgs with this status, Archiving
> volume group xxx, Is it normal? What can I do to solve this?
>
If you are creating lots of randomly named VGs - then you'll need to manual
prune /etc/lvm/archive directory.
When you use consistently the same VG name - you could configure some limits
via lvm.conf settings:
backup/retain_min
backup/retain_days
(Or you could disable backup completely)
Zdenek
prev parent reply other threads:[~2015-01-28 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 21:05 [linux-lvm] Slow response from lvs and vgs commands John Griffith
2015-01-19 22:21 ` Alasdair G Kergon
2015-01-19 22:58 ` John Griffith
2015-01-27 15:04 ` Marcos Dutra
2015-01-28 9:28 ` Zdenek Kabelac [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=54C8ABD0.4090402@redhat.com \
--to=zkabelac@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).