Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Feb 2014 16:56:37 -0500 (EST)
From:      Benjamin Kaduk <kaduk@MIT.EDU>
To:        mikej <mikej@mikej.com>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: ffs_fsync: dirty
Message-ID:  <alpine.GSO.1.10.1402241655530.1213@multics.mit.edu>
In-Reply-To: <c3e59d7269120184dac8102482dbd030@mail.mikej.com>
References:  <c3e59d7269120184dac8102482dbd030@mail.mikej.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

> I also get these LOR's but it never drops to the debugger.

These are well-known and harmless.

-Ben



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1402241655530.1213>