1834513 Members
2233 Online
110068 Solutions
New Discussion

pvchange and lvchange

 
SOLVED
Go to solution
Francis Noël
Regular Advisor

pvchange and lvchange

Hello Forum Heroes

Just need to confirm something with LVM here.
Using B.11.11 with MC/SG.

Did some pvchanges across the cluster to set the I/O timeout of all SAN PVs to 90 seconds.

Also "lvchange -r N" all the SAN lvols to disable Bad Block Relocation.

These parameters are recommended by the SAN manufacturer.

I'm pretty sure that changing the I/O timeout does not require reimporting all the VGs on the cluster nodes where they are inactive. Is this also the case with lvchange ? I think it is but I'd like be sure.

Thanks !
3 REPLIES 3
Siju Vadakkan
Trusted Contributor

Re: pvchange and lvchange

You don't need to update on the adoptive since it is updated in the LVM structure and all the configuration changes would be available on the adoptive node as well. I am pretty sure about that.
Steven E. Protter
Exalted Contributor
Solution

Re: pvchange and lvchange

Shalom,

You are right. I don't agree on the necessity of the changes. I working SAN should never have a problem with the default time outs.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Francis Noël
Regular Advisor

Re: pvchange and lvchange

Thanks guys

Agreed. The default timeouts are okay and I'd leave thme alone, but the company that built the storage says it has to be 90. Supported configurations and all that...