Setting Logical Volume Timeout (LVTO) on HP-UX 11/11i

[Jonathan F. Van Avery_2]

Does anyone know how you set the Logical Volume Timeout (LVTO) on HP-UX version 11 and 11i.

Thanks in advance,

Jonathan F. Van Avery

[Steve Hamilton_2]

Jonathan,

Check out the lvchange(1M) manpage, specifically the "-t" option. That allows you to specify a timeout on the Logical Volume level.

If you have several LVs on which you wish to change the timeout, then separate 'lvchange' commands will be needed...

Hope that helps...

Steve Hamilton
Beechglen Development
steveh@beechglen.com

[Jeff Schussele]

Hi Jonathan,

Use the following at the LV level:

lvchange -t XXX /dev/vg_name/lv_name # Where XXX equals timeout in seconds

Or at the PV level:

pvchange -t XXX /dev/dsk/cXtYdZ

HTH,
Jeff

[Mark Grant]

As far as I was aware, you can only do this with the physical volumes, not the logical volumes. COuld be wrong.

If you want to change ot on the physical volumes then its "pvchange -t seconds /dev/dsk/whatever"

[Mark Grant]

Shows how wrong it is possible to be :)

[Stuart Abramson_2]

lvchange -t.

However, why are you doing this? I have never heard of it before.

We do physical volume timeout changes, for our EMC disks. EMC recommends it.

pvchange -t 90 /dev/dsk/cXtYdZ.

[Robert-Jan Goossens]

Hi,

Check this doc,

Date: 8/25/97
Document description: How to adjust logical volume timeout variables
Document id: UNX1030078

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062952613

Robert-Jan

[Dietmar Konermann]

Be careful, Jonathan!

When setting an lvol timeout you must be absolutely sure what you're doing.

When the lvol timeout pops, even retryable IO errors are passed up to the above layers which need to be aware of how to handle them! E.g. a file system is a prominent example of not being aware, which means it is corrupted and needs checking then.

In generel lvol timeouts <> 0 are only for applications that work directly on raw devices and are able to handle those IO errors. The default '0' means 'retry forever for retryable errors'.

Best regards...
Dietmar.