From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Benjamin Marzinski" Subject: Re: no_path_retry: NO_PATH_RETRY_FAIL vs NO_PATH_RETRY_UNDEF Date: Mon, 7 Nov 2016 12:55:20 -0600 Message-ID: <20161107185520.GM1972@octiron.msp.redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Xose Vazquez Perez Cc: Kiyoshi Ueda , device-mapper development List-Id: dm-devel.ids 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.