From mboxrd@z Thu Jan 1 00:00:00 1970 From: Drew Hastings Subject: Re: multipath target and non-request-stackable devices Date: Wed, 31 Oct 2018 17:47:26 -0700 Message-ID: References: <20181031221402.GA22981@redhat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4032817620532692162==" Return-path: In-Reply-To: <20181031221402.GA22981@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: Mike Snitzer Cc: dm-devel@redhat.com List-Id: dm-devel.ids --===============4032817620532692162== Content-Type: multipart/alternative; boundary="000000000000e404ed05798fc304" --000000000000e404ed05798fc304 Content-Type: text/plain; charset="UTF-8" Perfect, thank you! For what it's worth, the error did not happen with regular, locally attached NVME devices. It only occurred with NVMEoF devices, with the chelsio driver shipped with the kernel. You seemed to discuss this a bit in https://www.redhat.com/archives/dm-devel/2016-June/msg00430.html Anyway, this solves it for me. Thanks again! --000000000000e404ed05798fc304 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Perfect, thank you!

Fo= r what it's worth, the error did not happen with regular, locally attac= hed NVME devices. It only occurred with NVMEoF devices, with the chelsio dr= iver shipped with the kernel. You seemed to discuss this a bit in=C2=A0ht= tps://www.redhat.com/archives/dm-devel/2016-June/msg00430.html

Anyway, this solves it for me. Thanks again!
--000000000000e404ed05798fc304-- --===============4032817620532692162== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============4032817620532692162==--