Re: multipath-tools: Standardization of no_path_retry

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/12/2017 11:41 PM, Xose Vazquez Perez wrote:
> Hi,
> 
> There are plenty of arbitrary values:
> 
>       1                 .no_path_retry = 5,
>       1                 .no_path_retry = 6,
>       3                 .no_path_retry = 10,
>       8                 .no_path_retry = 12,
>       2                 .no_path_retry = 15,
>       6                 .no_path_retry = 18,
>       1                 .no_path_retry = 24,
>      37                 .no_path_retry = 30,
>       4                 .no_path_retry = (300 / DEFAULT_CHECKINT),
> 
> 
>      19                 .no_path_retry = NO_PATH_RETRY_QUEUE,
>      15       (Default) .no_path_retry = NO_PATH_RETRY_UNDEF,
> 
> 
> 
> Any thoughts about this?
> 
These are typically coming from vendor hardware entries, and in most
cases they are set on request from the vendor.
So unless someone has actually _tested_ with a different setting on that
array we should rather leave them alone.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@xxxxxxx			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel




[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux