Re: [linux-lvm] Why does every lvm command insist on touching every pv?

[Takahiro Yasui <tyasui@redhat.com>]

On 06/18/10 13:10, Takahiro Yasui wrote:
> 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.

I'm sorry. My explanation was not good. Only PV1-3 are updated and
PV4-6 are not. LVM command have always behaved like this.

I should have added an more sentence like

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. So PV4-6 don't necessarily
need to be accessed.

Sorry for making you confused.

Thanks,
Taka