From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: v4.8 dm-mpath Date: Tue, 16 Aug 2016 22:43:02 -0400 Message-ID: <20160817024302.GA29089@redhat.com> References: <20160816191241.GA16948@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20160816191241.GA16948@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Bart Van Assche Cc: device-mapper development List-Id: dm-devel.ids On Tue, Aug 16 2016 at 3:12pm -0400, Mike Snitzer wrote: > On Tue, Aug 16 2016 at 1:32pm -0400, > Bart Van Assche wrote: > > > Can you have a look at this? > > I'll get linux-dm.git's 'dm-4.8' branch (v4.8-rc2) loaded on one of my > testbed systems to run the mptest testsuite. It should provide coverage > for simple failover and failback. I successfully ran mptest against that v4.8-rc2 based kernel. Any chance you could try mptest to see if it also passes for you? Or if it is able to trigger the issue for you. mptest's runtest script defaults to setting up scsi-mq and dm-mq.