linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Why does every lvm command insist on touching	every pv?
Date: Tue, 15 Jun 2010 17:47:09 +0100	[thread overview]
Message-ID: <20100615164709.GG15698@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4C179B03.2000102@cfl.rr.com>

On Tue, Jun 15, 2010 at 11:23:47AM -0400, Phillip Susi wrote:
> Every time I run any lvm command, it goes out and touches every pv,
> causing all the disks to wake up from standby.  Why is this?  Shouldn't
> a simple lvs command be able to look in the /etc/lvm/cache for what it
> needs instead of touching every pv, even ones with no lvs on them?
 
It shouldn't normally scan unless it detects something might have changed, but
if you know the volume group name(s) already, put them on the command line: 
  lvs vg1 vg2

(As always -vvvv may give you clues as to what is triggering the scan.)

Alasdair

  reply	other threads:[~2010-06-15 16:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 15:23 [linux-lvm] Why does every lvm command insist on touching every pv? Phillip Susi
2010-06-15 16:47 ` Alasdair G Kergon [this message]
2010-06-15 17:46   ` Phillip Susi
2010-06-15 19:17     ` Takahiro Yasui
2010-06-15 20:24       ` Phillip Susi
2010-06-15 20:41         ` Takahiro Yasui
2010-06-16  0:34           ` Phillip Susi
2010-06-16  9:30             ` Zdenek Kabelac
2010-06-16 19:27               ` Takahiro Yasui
2010-06-17  8:23                 ` Zdenek Kabelac
2010-06-17 13:53                   ` Takahiro Yasui
2010-06-18 14:27                     ` Zdenek Kabelac
2010-06-18 14:50                       ` Takahiro Yasui
2010-06-18 15:52                         ` Alasdair G Kergon
2010-06-18 17:10                           ` Takahiro Yasui
2010-06-18 18:55                             ` Takahiro Yasui
2010-06-16 14:52             ` Takahiro Yasui

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=20100615164709.GG15698@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=psusi@cfl.rr.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).