Date: Tue, 12 Apr 2005 03:29:27 +0800 From: Rong-En Fan <grafan@gmail.com> To: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> Cc: stable@freebsd.org Subject: Re: 5.3-S (Mar 6) softdep stack backtrace from getdirtybuf()... problem? Message-ID: <6eb82e05041112292f93e2d5@mail.gmail.com> In-Reply-To: <1113160601.37307.9.camel@rushlight.kf8nh.com> References: <1113160601.37307.9.camel@rushlight.kf8nh.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 11, 2005 3:16 AM, Brandon S. Allbery KF8NH <allbery@ece.cmu.edu> wrote: > I have twice so far had the kernel syslog a stack backtrace with no > other information. Inspection of the kernel source, to the best of my > limited understanding, suggests that getdirtybuf() was handed a buffer > without an associated vnode. Kernel config file and make.conf attached. > > Should I be concerned? > > Note that this system is an older 600MHz Athlon with only 256MB RAM, and > both times this triggered it was thrashing quite a bit (that's more or > less its usual state...). I saw these similar trace on a 5.4-RC1/amd64 with 9 NFS mount. I suspect this is a issue with busy NFS server? rafan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e05041112292f93e2d5>