From: Vladislav Bogdanov <bubble@hoster-ok.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] cLVM commands often taking a long time to execute
Date: Thu, 10 Nov 2011 12:05:52 +0300 [thread overview]
Message-ID: <4EBB93F0.8070901@hoster-ok.com> (raw)
In-Reply-To: <3D44B3DCE57399449CC1391C2AD6EC4C16EA8D76@ORSMSX101.amr.corp.intel.com>
09.11.2011 03:06, Riches Jr, Robert M wrote:
> I�m running into some odd behavior from clustered LVM commands on a
> 3-node pacemaker-based cluster. When other processes on the nodes are
> doing somewhat heavy sequential I/O traffic, LVM commands such as lvs,
> pvs, vgs, lvdisplay, pvdisplay, and vgdisplay have widely variable,
> often very long execution times. The same LVM command done repetitively
> will have execution times varying from less than a second to 10-15
> seconds, more rarely up to around 60 seconds. Other read-heavy commands
> such as find, wc, and sum have much less variability and much shorter
> tails in the distribution of their execution times.
>
> Is it known what causes the cLVM commands to be so slow at times?
>
> Perchance, are there known ways to get cLVM commands to be less slow?
I use chrt -r 99 for them. And I also run clvmd the same way. But this
is much more about CPU load then IO load.
Also, please make sure that you correctly filter unneeded block devices
from being PV-suspects (filter clause in lvm.conf).
Best,
Vladislav
next prev parent reply other threads:[~2011-11-10 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 0:06 [linux-lvm] cLVM commands often taking a long time to execute Riches Jr, Robert M
2011-11-10 9:05 ` Vladislav Bogdanov [this message]
2011-11-10 16:16 ` Riches Jr, Robert M
2011-11-15 7:58 ` Vladislav Bogdanov
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=4EBB93F0.8070901@hoster-ok.com \
--to=bubble@hoster-ok.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.