[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames

[ChristianEhrhardt]

Hi Clayton,
I'm cleaning up bugs that work was going on but were forgotten for whatever reason.
Sorry for the delay (again I should say).

To build and use from source you can:
# Build from git
$ git clone https://github.com/open-iscsi/open-iscsi.git
$ sudo apt build-dep open-iscsi
$ sudo apt-get install libssl-dev
$ cd open-iscsi
# Now this step depends on compiler, libs and more - e.g. I had to comment a few lines in include/iscsi_proto.h whicih were now in the linux-headers before being able to build correctly
$ make
$ make install
# Remove the packages version, but backup config
$ cp -a /etc/iscsi ~/iscsi-etc-backup
$ apt remove --purge open-iscsi
# Install what you just built and make it usable
$ systemctl daemon-reload
$ systemctl start open-iscsi
$ systemctl status open-iscsi

As usual you have the config in "/etc/iscsi/" and can try to experiment with that.
Use your backup at ~/iscsi-etc-backup to configure it as similar as possible to the former case.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to open-iscsi in Ubuntu.
https://bugs.launchpad.net/bugs/1615694

Title:
  [860730] Host experiencing constant session termination and recreation
  while using jumbo frames

Status in open-iscsi package in Ubuntu:
  Triaged

Bug description:
  We're seeing constant iSCSI session terminations and subsequent
  recreations on Ubuntu 16.04 hosts running IO to an E-Series Array
  using Jumbo Frames. We've pulled trace of the issue to determine a
  root cause and discovered that the host appears to be overrunning the
  Max Command Sequence Number set by the Target. The target is responds
  to this be killing that session and recreating a new one in it's place
  as an error recovery mechanism, so the crux of the issue is why the
  host seems to be falling outside of iSCSI compliance and overrunning
  the Max Command Sequence Number. This is the reason I went ahead and
  filed the bug against open-iscsi.

  Attached are actually two separate traces from two separate recreate,
  one a Finisar Analyzer Trace, the other a typical TCP dump view-able
  through wire-shark. I've also attached the Apport data for open-iscsi
  in case that could be of any use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1615694/+subscriptions