Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Aug 2003 10:26:08 +0200
From:      Christian Brueffer <chris@unixpages.org>
To:        Tim Robbins <tjr@FreeBSD.ORG>
Cc:        current@FreeBSD.ORG
Subject:   Re: panic: bundirty: buffer 0xc776e118 still on queue 2
Message-ID:  <20030821082608.GM638@unixpages.org>
In-Reply-To: <20030821075728.GA54713@dilbert.robbins.dropbear.id.au>
References:  <20030820222607.GA638@unixpages.org> <20030821034054.GA54061@dilbert.robbins.dropbear.id.au> <20030821061445.GK638@unixpages.org> <20030821075728.GA54713@dilbert.robbins.dropbear.id.au>

next in thread | previous in thread | raw e-mail | index | archive | help

--Mh8CTEa8Ax54aLHp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:
>=20
> > 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:
> > >=20
> > > > Hi,
> > > >=20
> > > > just got a panic on following 5.1-CURRENT machine:
> > > >=20
> > > > FreeBSD gondor.middleearth 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Thu =
Aug
> > > > 7 21:32:39 CEST 2003     chris@haa konia.hitnet.rwth-aachen.de:/usr=
/obj/usr/src/sys/GONDOR  i386
> > > >=20
> > > > A dump is available if anyone needs specific information.
> > > [...]
> > > > panic: bundirty: buffer 0xc776e118 still on queue 2^M
> > > [...]
> > > > #2  0xc0254007 in panic (fmt=3D0xc03cc0ef "bundirty: buffer %p stil=
l on queue %d")^M
> > > >      at /usr/src/sys/kern/kern_shutdown.c:550^M
> > > > #3  0xc029b291 in bundirty (bp=3D0xc776e118) at /usr/src/sys/kern/v=
fs_bio.c:1121^M
> > > > #4  0xc029bde1 in brelse (bp=3D0xc776e118) at /usr/src/sys/kern/vfs=
_bio.c:1436^M
> > > > #5  0xc02efcb8 in nfs_writebp (bp=3D0xc776e118, force=3D1, td=3D0xc=
2c17e40)^M
> > > >          at /usr/src/sys/nfsclient/nfs_vnops.c:2987^M
> > > > #6  0xc02e02c3 in nfs_bwrite (bp=3D0x0) at /usr/src/sys/nfsclient/n=
fs_bio.c:76^M
> > > > #7  0xc029dd41 in getblk (vp=3D0xc2c77b68, blkno=3D400, size=3D1536=
0, slpflag=3D256, slptimeo=3D0, flags=3D0)^M
> > > > 	     at /usr/src/sys/kern/vfs_bio.c:2512^M
> > > > #8  0xc02e21e5 in nfs_getcacheblk (vp=3D0xc2c77b68, bn=3D400, size=
=3D15360, td=3D0xc2c17e40)^M
> > > > 	         at /usr/src/sys/nfsclient/nfs_bio.c:1037^M
> > >=20
> > > 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 entr=
ies from
> > > /etc/fstab (with any private data removed) would be helpful in tracki=
ng this
> > > problem down.
> > >=20
> >=20
> > No, all mounts were read-write.
>=20
> Did one of the servers go down shortly before the panic, then? The last f=
ew
> lines of dmesg might be useful.
>=20

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

--=20
Christian Brueffer	chris@unixpages.org	brueffer@FreeBSD.org
GPG Key:	 http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D

--Mh8CTEa8Ax54aLHp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/RIIgbHYXjKDtmC0RAqdEAKC4O3m7T3Gnl0WGDQ2LI8iyf2f2xQCfdeZ8
iOmwx948dfY0k1j9NSW65RM=
=6VOi
-----END PGP SIGNATURE-----

--Mh8CTEa8Ax54aLHp--



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