From owner-freebsd-net@freebsd.org  Sun Nov 12 17:54:24 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 716F4C31CF1
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sun, 12 Nov 2017 17:54:24 +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 5FFE06F2C0
 for <freebsd-net@FreeBSD.org>; Sun, 12 Nov 2017 17:54:24 +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 vACHsNqG021781
 for <freebsd-net@FreeBSD.org>; Sun, 12 Nov 2017 17:54:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 191916] pflogd(8) eats cpu and hangs with
 net.bpf.zerocopy_enable=0
Date: Sun, 12 Nov 2017 17:54:23 +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: 9.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mg@fork.pl
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Overcome By Events
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-191916-2472-nAdOeq1fA8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191916-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-191916-2472@https.bugs.freebsd.org/bugzilla/>
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-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Nov 2017 17:54:24 -0000

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

Marcin Gryszkalis <mg@fork.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mg@fork.pl

--- Comment #4 from Marcin Gryszkalis <mg@fork.pl> ---
Note for those with similar problem: I just noticed same effect (pflogd eat=
ing
100% cpu on initializing). It was because mistake in newsyslog.conf that
stopped /var/log/pflog rotation and the log file grown to over 20GB.=20

As pflogd(8) says:

     pflogd tries to preserve the integrity of the log file against I/O
     errors.  Furthermore, integrity of an existing log file is verified
     before appending.

--=20
You are receiving this mail because:
You are the assignee for the bug.=