Re: panic: bundirty: buffer 0xc776e118 still on queue 2

On Thu, Aug 21, 2003 at 05:57:28PM +1000, Tim Robbins wrote:
> On Thu, Aug 21, 2003 at 08:14:45AM +0200, Christian Brueffer wrote:
> 
> > On Thu, Aug 21, 2003 at 01:40:54PM +1000, Tim Robbins wrote:
> > > On Thu, Aug 21, 2003 at 12:26:07AM +0200, Christian Brueffer wrote:
> > > 
> > > > Hi,
> > > > 
> > > > just got a panic on following 5.1-CURRENT machine:
> > > > 
> > > > FreeBSD gondor.middleearth 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Thu Aug
> > > > 7 21:32:39 CEST 2003     chris_at_haa konia.hitnet.rwth-aachen.de:/usr/obj/usr/src/sys/GONDOR  i386
> > > > 
> > > > A dump is available if anyone needs specific information.
> > > [...]
> > > > panic: bundirty: buffer 0xc776e118 still on queue 2^M
> > > [...]
> > > > #2  0xc0254007 in panic (fmt=0xc03cc0ef "bundirty: buffer %p still on queue %d")^M
> > > >      at /usr/src/sys/kern/kern_shutdown.c:550^M
> > > > #3  0xc029b291 in bundirty (bp=0xc776e118) at /usr/src/sys/kern/vfs_bio.c:1121^M
> > > > #4  0xc029bde1 in brelse (bp=0xc776e118) at /usr/src/sys/kern/vfs_bio.c:1436^M
> > > > #5  0xc02efcb8 in nfs_writebp (bp=0xc776e118, force=1, td=0xc2c17e40)^M
> > > >          at /usr/src/sys/nfsclient/nfs_vnops.c:2987^M
> > > > #6  0xc02e02c3 in nfs_bwrite (bp=0x0) at /usr/src/sys/nfsclient/nfs_bio.c:76^M
> > > > #7  0xc029dd41 in getblk (vp=0xc2c77b68, blkno=400, size=15360, slpflag=256, slptimeo=0, flags=0)^M
> > > > 	     at /usr/src/sys/kern/vfs_bio.c:2512^M
> > > > #8  0xc02e21e5 in nfs_getcacheblk (vp=0xc2c77b68, bn=400, size=15360, td=0xc2c17e40)^M
> > > > 	         at /usr/src/sys/nfsclient/nfs_bio.c:1037^M
> > > 
> > > I think I recognise this backtrace. Did you have a read-only NFS mount
> > > active at the time of the crash? In any case, a copy of your NFS entries from
> > > /etc/fstab (with any private data removed) would be helpful in tracking this
> > > problem down.
> > > 
> > 
> > No, all mounts were read-write.
> 
> Did one of the servers go down shortly before the panic, then? The last few
> lines of dmesg might be useful.
> 

No indication for that in the logs.  I would have noticed anyway, as I was
playing music from one of the shares.
One of the shared file systems was full (besides the reserved space) at the
time of the panic.  Could that have to do something with it?

- Christian

-- 
Christian Brueffer	chris_at_unixpages.org	brueffer_at_FreeBSD.org
GPG Key:	 http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D