From owner-freebsd-bugs@freebsd.org Thu Aug 3 13:58:56 2017 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 67E11DBE464 for ; Thu, 3 Aug 2017 13:58:56 +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 3CFAD7D337 for ; Thu, 3 Aug 2017 13:58:56 +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 v73DwunO090448 for ; Thu, 3 Aug 2017 13:58:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221202] Mbufs leak since r321253 Date: Thu, 03 Aug 2017 13:58:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gergely.czuczy@harmless.hu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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, 03 Aug 2017 13:58:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221202 Bug ID: 221202 Summary: Mbufs leak since r321253 Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: gergely.czuczy@harmless.hu Hello, While running some port builds over an NFS-mounted /usr/ports on my=20 aarch64 VM after r321253, I've noticed that sooner or later I'm getting=20 an error saying "kernel: [zone: mbuf_cluster] kern.ipc.nmbclusters limit=20 reached". I've tried increasing the sysctl, but after some time I always=20 got the error. I've checked the mbuf counter with ``netstat -m'' periodically during=20 the build, and noticed that the mbufs in use and mbuf clusters in use=20 are continuously increasing, I've never seen a decrease: 279943/392/280335 mbufs in use (current/cache/total) 130819/253/131072/131072 mbuf clusters in use (current/cache/total/max) According to=20 https://svnweb.freebsd.org/base/head/?view=3Dlog&pathrev=3D321253, the=20 previous commit to HEAD was r321248. I've checked it on that build as=20 well, and I couldn't reproduce the issue, mbuf counters were stable. After getting the kernel error message, the builds got stuck, some=20 processes become unresponsive, and the only way to I was aware to clear=20 the mbufs was to reboot the VM. So far what I know, is building over NFS triggers the leak. However, I=20 haven't tested it with other network activities, might also do the trick. Could you please take a look into it? If any more information is needed, please let me know, I still have my=20 test VMs at hand, I can do a few tests. Best regards, Gergely PS1: Might affect other architectures as well, I haven't tested it on anyth= ing else than aarch64. --=20 You are receiving this mail because: You are the assignee for the bug.=