On 01/29/2016 02:41 PM, Mike Christie wrote: > On 01/29/2016 02:31 PM, Christian Seiler wrote: >> > On 01/29/2016 09:07 PM, Mike Christie wrote: >>> >> On 01/27/2016 05:17 PM, Christian Seiler wrote: >>>> >>> The test setup is quite simple: LIO target running on the host with >>>> >>> fileio backend (I tried both Debian Jessie host with 3.16 kernel and >>>> >>> Ubuntu 15.04 host with 3.19 kernel, no difference), initiator >>>> >>> running inside a libvirt/KVM instance (Debian sid); nothing special >>>> >>> about the setup otherwise. (The target itself shows no problems.) >>> >> >>> >> So there are no other log messages on the LIO box? Something about max >>> >> sectors being violated or a memory allocation failure? >> > >> > I didn't notice that earlier, but I get: >> > >> > kernel: fd_do_rw() write returned -22 >> > >> > (-22 is -EINVAL) >> > >> > Weird. I could have sworn that when I first encountered the problem >> > I didn't see anything in the target's logs... Obviously I'm mistaken >> > and I'm very sorry that I didn't notice that earlier. >> > >>> >> What kernel version is LIO running on in these tests? >> > >> > LIO targets I've tried: >> > - 3.16.7-ckt20 (Debian Jessie) >> > - 3.19.0-43-generic (Ubuntu 15.04) >> > >> > I'll try a newer version tomorrow and see if the problem >> > persists.
When you login to the target do a sg_inq -p 0xb0 /dev/sdX and check if the optimal/max transfer lengths are 0. For the newer versions it should give you a non zero value. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
