> -----Original Message----- > From: David Disseldorp [mailto:ddiss@xxxxxxx] > Sent: 06 April 2017 14:06 > To: Nick Fisk <nick@xxxxxxxxxx> > Cc: 'Maged Mokhtar' <mmokhtar@xxxxxxxxxxx>; 'Brady Deetz' > <bdeetz@xxxxxxxxx>; 'ceph-users' <ceph-users@xxxxxxxx> > Subject: Re: rbd iscsi gateway question > > X-Assp-URIBL failed: 'suse.de'(black.uribl.com ) > X-Assp-Spam-Level: ***** > X-Assp-Envelope-From: ddiss@xxxxxxx > X-Assp-Intended-For: nick@xxxxxxxxxx > X-Assp-ID: ASSP.fisk.me.uk (49148-08075) > X-Assp-Version: 1.9.1.4(1.0.00) > > Hi, > > On Thu, 6 Apr 2017 13:31:00 +0100, Nick Fisk wrote: > > > > I believe there > > > was a request to include it mainstream kernel but it did not happen, > > > probably waiting for TCMU solution which will be better/cleaner design. > > Indeed, we're proceeding with TCMU as a future upstream acceptable > implementation. > > > Yes, should have mentioned this, if you are using the suse kernel, > > they have a fix for this spiral of death problem. > > I'm not to sure what you're referring to WRT the spiral of death, but we did > patch some LIO issues encountered when a command was aborted while > outstanding at the LIO backstore layer. > These specific fixes are carried in the mainline kernel, and can be tested > using the AbortTaskSimpleAsync libiscsi test. Awesome, glad this has finally been fixed. Death spiral was referring to when using it with ESXi, both the initiator and target effectively hang forever and if you didn't catch it soon enough, sometimes you end up having to kill all vm's and reboot hosts. Do you know what kernel version these changes would have first gone into? I thought I looked back into this last summer and it was still showing the same behavior. > > Cheers, David _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |