[Bug 242621] iscsi initiator does not provide devices after reconnection

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621

Mark Linimon <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|***@FreeBSD.org |***@FreeBSD.org
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
To unsubscribe, send any mail to "freebsd-scsi-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621

Ben RUBSON <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #1 from Ben RUBSON <***@gmail.com> ---
Do you use jumbo frames ?
Could be lack of mbuf_jumbo_9k (vmstat -z should tell you).
If so, a workaround is to decrease the MTU until 9K mbufs are not more used.
On my systems it gives a 4072 bytes MTU.
Of course it's just a workaround, as decreasing MTU increases overhead...
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
To unsubscribe, send any mail to "freebsd-scsi-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621

--- Comment #2 from ***@dominicschlegel.ch ---
(In reply to Ben RUBSON from comment #1)

no, we do not use jumbo frames:

[***@xxx:~] # ifconfig | grep mtu
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
enc0: flags=0<> metric 0 mtu 1536
pfsync0: flags=0<> metric 0 mtu 1500
pflog0: flags=0<> metric 0 mtu 33160
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
lagg0.10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
lagg0.800: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

[***@xxx:~] # vmstat -z | grep mbuf_jumbo_9k
mbuf_jumbo_9k: 9216, 2420071, 0, 0, 0, 0, 0
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
To unsubscribe, send any mail to "freebsd-scsi-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621

--- Comment #3 from commit-***@freebsd.org ---
A commit references this bug:

Author: meta
Date: Wed Jan 15 04:30:48 UTC 2020
New revision: 523079
URL: https://svnweb.freebsd.org/changeset/ports/523079

Log:
sysutils/getssl: Update to 2.14

2.14
* Rebased master onto APIv2 and added Content-Type: application/jose+json

PR: 242621
Submitted by: sanpei
Approved by: maintainer timeout

Changes:
head/sysutils/getssl/Makefile
head/sysutils/getssl/distinfo
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
To unsubscribe, send any mail to "freebsd-scsi-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621

Edward Tomasz Napierala <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org

--- Comment #4 from Edward Tomasz Napierala <***@FreeBSD.org> ---
Can you enable debug messages (sysctl kern.iscsi.debug=10) and paste dmesg from
when it happens? Also, instead of rebooting, can you instead try 'iscsictl -M
-e off' and then 'iscsictl -M -e on'?
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-***@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
To unsubscribe, send any mail to "freebsd-scsi-***@freebsd.org"

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242621

--- Comment #5 from ***@dominicschlegel.ch ---
(In reply to Edward Tomasz Napierala from comment #4)

we still have issues with this under 12.3-RELEASE-p1. meanwhile i came across
such a situation again and have some more information now:

when this situation occurs 'iscsictl -M -e off' and then 'iscsictl -M -e on'
does not help at all. even a normal `shutdown -r now` is at one point of the
shutdown routine not progressing anymore and somehow waiting for iscsi devices.
so we are forced to reset the server at this stage.