[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dm-devel
Subject:    Re: [dm-devel] no_path_retry: NO_PATH_RETRY_FAIL vs NO_PATH_RETRY_UNDEF
From:       "Benjamin Marzinski" <bmarzins () redhat ! com>
Date:       2016-11-07 18:55:20
Message-ID: 20161107185520.GM1972 () octiron ! msp ! redhat ! com
[Download RAW message or body]

On Mon, Nov 07, 2016 at 05:11:33PM +0100, Xose Vazquez Perez wrote:
> Hi,
> 
> 
> NO_PATH_RETRY_UNDEF is 0
> 
> 
> no_path_retry    Specify what to do when all paths are down. Possible values are:
> 
>                     value > 0   number of retries until disable I/O queueing.
> 
>                     fail        for immediate failure (no I/O queueing).
> 
>                     queue       for never stop I/O queueing. Similar to queue_if_no_path.
> 
> 
> 
> Is there any real difference?

The idea was that if you have NO_PATH_RETRY_UNDEF, then you just use
whatever is in the features line. If you have NO_PATH_RETRY_FAIL, that
takes priority over the features line.

So if someone has

features "1 queue_if_no_path"

then NO_PATH_RETRY_UNDEF gets you the same results as
NO_PATH_RETRY_QUEUE.

-Ben

> 
> 
> Thank you.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
[prev in list] [next in list] [prev in thread] [next in thread]