From owner-freebsd-bugs@freebsd.org Thu Nov 10 23:47:16 2016 Return-Path: Delivered-To: freebsd-bugs@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 C4A40C3B9A9 for ; Thu, 10 Nov 2016 23:47:16 +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 B471416D6 for ; Thu, 10 Nov 2016 23:47:16 +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 uAANlG26025087 for ; Thu, 10 Nov 2016 23:47:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211990] iscsi fails to reconnect and does not release devices Date: Thu, 10 Nov 2016 23:47:16 +0000 X-Bugzilla-Reason: AssignedTo 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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 23:47:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211990 --- Comment #31 from Julien Cigar --- Y(In reply to Steven Hartland from comment #29) Yes it seems so: root@filer1:/var/log # vmstat -z | head -n 1; vmstat -z | grep mbuf ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP mbuf_packet: 256, 3200070, 1024, 3431,94881716, 0, 0 mbuf: 256, 3200070, 257, 3103,566359041, 0, 0 mbuf_cluster: 2048, 500010, 4455, 133,15367798, 0, 0 mbuf_jumbo_page: 4096, 250005, 0, 161,102798544, 0, 0 mbuf_jumbo_9k: 9216, 74075, 256, 120,52036055, 304, 0 mbuf_jumbo_16k: 16384, 41667, 0, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0, 0, 0 > You'd have to catch it when the issue is occurring to confirm not so easy :) but every time I have a WARNING: 10.20.30.32 (iqn.2016-08.lan.prod:target0): no ping reply (NOP-In) after 30 seconds; reconnecting I have a small increase in the "requests for 9k jumbo clusters denied" coun= ter > If you have plenty of ram you could just trying doubling kern.ipc.nmbjumb= o9 to see if the problem goes away? The machine has only 8GB of RAM (and ZFS), I think I'll first test with a 1= 500 MTU and -tso --=20 You are receiving this mail because: You are the assignee for the bug.=