Date: Thu, 28 Mar 2002 10:58:11 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Daniel Schales <dan@coes.LaTech.edu> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: nfs_fsync: not dirty error in 4.5-RELEASE Message-ID: <200203281858.g2SIwBg32227@apollo.backplane.com> References: <20020327221059.L45447-100000@stardust.latech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:On Wed, 27 Mar 2002, Wilko Bulte wrote:
:
:> OK. I suppose you might want to try to catch a panic dump if you can.
:>
:
:I don't think it's the maxusers setting. I filed a PR on this last week,
:my maxusers was set to 0. The PR contains a back trace as well.
:I don't have the number handy. I am running 4.5-STABLE (early March)
:and have experienced this on three different systems.
:
:Danny
If someone can get a kernel.debug and panic dump together showing
the problem, I'll try to track it down. It may require some diagnostic
code, though, to record who cleared B_DELWRI on the buffer in question.
From my quick perusal the panic is correct... NFS is pulling a buffer
off the vnode's dirty queue and that buffer is expected to have B_DELWRI
set on it.
If reducing kern.maxfiles stops the problem from occuring then the
bug could be an indrect effect of some other system resource running
out.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203281858.g2SIwBg32227>