From owner-freebsd-fs@FreeBSD.ORG Mon Feb 24 22:25:17 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 059229A6 for ; Mon, 24 Feb 2014 22:25:17 +0000 (UTC) Received: from chez.mckusick.com (chez.mckusick.com [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CD9811DE9 for ; Mon, 24 Feb 2014 22:25:16 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id s1OMPBed043219; Mon, 24 Feb 2014 14:25:11 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201402242225.s1OMPBed043219@chez.mckusick.com> To: Benjamin Kaduk Subject: Re: ffs_fsync: dirty In-reply-to: Date: Mon, 24 Feb 2014 14:25:11 -0800 From: Kirk McKusick Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2014 22:25:17 -0000 > Date: Mon, 24 Feb 2014 16:56:37 -0500 (EST) > From: Benjamin Kaduk > To: mikej > Subject: Re: ffs_fsync: dirty > Cc: freebsd-fs@freebsd.org > > On Sun, 23 Feb 2014, mikej wrote: > >> FreeBSD custom 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261885: Fri Feb 14 >> 08:51:48 EST 2014 mikej@custom:/usr/obj/usr/src/sys/GENERIC amd64 >> >> I get a bunch of these while running poudriere. >> >> ffs_fsync: dirty >> 0xfffff808e200e3b0: tag ufs, type VDIR >> usecount 1, writecount 0, refcount 8 mountedhere 0 >> flags (VI_ACTIVE) >> v_object 0xfffff8039e934300 ref 0 pages 38 cleanbuf 1 dirtybuf 4 >> lock type ufs: EXCL by thread 0xfffff8021bf72920 (pid 48820, cpdup, tid >> 100292) >> ino 1527731, on dev mfid0p2 > > That is a potentially interesting violation caught by INVARIANTS. I don't > think I have time to investigate right now, though. > > -Ben The above output is rather vexing, but its only bad effect is to waste a bit of memory. Several of us (kib, jeff, and myself) have tried to track it down without success. Hopefully we will get it sorted out before too much longer. But other more pressing problems keep this one on the back burner. Kirk McKusick