Date: Mon, 24 Feb 2014 14:25:11 -0800 From: Kirk McKusick <mckusick@mckusick.com> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: freebsd-fs@freebsd.org Subject: Re: ffs_fsync: dirty Message-ID: <201402242225.s1OMPBed043219@chez.mckusick.com> In-Reply-To: <alpine.GSO.1.10.1402241655530.1213@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Mon, 24 Feb 2014 16:56:37 -0500 (EST) > From: Benjamin Kaduk <kaduk@MIT.EDU> > To: mikej <mikej@mikej.com> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402242225.s1OMPBed043219>