linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Why does every lvm command insist on touching	every pv?
Date: Fri, 18 Jun 2010 13:10:09 -0400	[thread overview]
Message-ID: <4C1BA871.9030800@redhat.com> (raw)
In-Reply-To: <20100618155245.GH15698@agk-dp.fab.redhat.com>

On 06/18/10 11:52, Alasdair G Kergon wrote:
> On Fri, Jun 18, 2010 at 10:50:41AM -0400, Takahiro Yasui wrote:
>> For example, there are six PVs and two VGs as below:
>>
>>   VG1: PV1, PV2, PV3
>>   VG2: PV4, PV5, PV6
>>
>> If we create a new LV or delete VG1, then metadatas on only PV1, PV2, PV3
>> need to be updated but not for PV4, PV5, PV6.
>  
> Correct - and the tools have always behaved like that!

Did I miss something? Or can we configure lvm.conf to make lvm
commands behave like that? That's the first topic we were talking
about. As far as I use lvm commands, they don't behave as I expected.

Thanks,
Taka

  reply	other threads:[~2010-06-18 17:10 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
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 [this message]
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=4C1BA871.9030800@redhat.com \
    --to=tyasui@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).