From owner-freebsd-scsi@freebsd.org Wed Nov 30 09:19:39 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EA90C5A857 for ; Wed, 30 Nov 2016 09:19:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0EB3817DE for ; Wed, 30 Nov 2016 09:19:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAU9Jcb8003447 for ; Wed, 30 Nov 2016 09:19:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Wed, 30 Nov 2016 09:19:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2016 09:19:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #33 from Julien Cigar --- an update on this: I turned off jumbo frames and TSO on the replication interface and the issue hasn't been repeated until now...! filer1% uptime 10:15AM up 18 days, 13:35, 1 user, load averages: 0.07, 0.09, 0.08 filer1% vmstat -z|head -1;vmstat -z|grep -i 'mbuf' ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP mbuf_packet: 256, 3200070, 1024, 3403,527205862, 0, 0 mbuf: 256, 3200070, 6, 2752,456285246, 0, 0 mbuf_cluster: 2048, 500010, 4427, 355,18287308, 0, 0 mbuf_jumbo_page: 4096, 250005, 0, 71, 2682330, 0, 0 mbuf_jumbo_9k: 9216, 74075, 0, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 41667, 0, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0, 0, 0 filer1% netstat -m 1031/6154/7185 mbufs in use (current/cache/total) 1024/3758/4782/500010 mbuf clusters in use (current/cache/total/max) 1024/3403 mbuf+clusters out of packet secondary zone in use (current/cache) 0/71/71/250005 4k (page size) jumbo clusters in use (current/cache/total/ma= x) 0/0/0/74075 9k jumbo clusters in use (current/cache/total/max) 0/0/0/41667 16k jumbo clusters in use (current/cache/total/max) 2305K/9338K/11644K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile filer1% netstat -I bge1 Name Mtu Network Address Ipkts Ierrs Idrop Opkts O= errs Coll bge1 1500 xx:xx:xx:xx:xx:xx 497577171 0 0 262946639= =20=20=20=20 0 0 bge1 - 10.20.30.0 10.20.30.31 497575590 - - 262942638= =20=20=20=20 - - filer1% ifconfig bge1 bge1: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3Dc009b ether xx:xx:xx:xx:xx:xx inet 10.20.30.31 netmask 0xffffff00 broadcast 10.20.30.255=20 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active (I'll let you know if the problem occurs again) --=20 You are receiving this mail because: You are on the CC list for the bug.=