> Well, I was about to chime in, but I couldn't manage to build myself a kernel
> with support for kdb without it crashing on me. I am seeing the same assert
> being tripped, and this is with the CVS tree built from about 4pm yesterday.
OK, I thought we had this fixed, I ran some fairly heavy tests on a
debug kernel, are you sure everything was uptodate and rebuilt from
the current code base?
> My Stats:
> - 10G XFS partition, built with mkfs.xfs from the 4pm yesterday CVS, wi
> th no additional options, mounted with no additional options
> - Debian/Unstable
> - Debian's default GCC was used to build: "CVS gcc-2_95-branch (dated 2
> - KNFSD was enabled, but no clients were accessing, no was there anythi
> ng exported.
> If there is anything else I can do, let me know.
> On Sat, Apr 07, 2001 at 09:46:10PM +0200, KELEMEN Peter wrote:
> > Hello,
> > After a couple of assertion failure-free months, here's a
> > reproducible one. I can trigger this by compiling the kernel tree
> > on a 500M XFS partition, on a Celeron 300 MHz 128M IDE machine.
> > Attempting to unmount the filesystem after the assertion has been
> > triggered hangs the umount process:
> > sys_oldumount->sys_umount->do_umount->shrink_dcache_sb->iput
> > ->linvfs_put_inode->vn_put->xfs_inactive->xfs_inactive_free_eofblocks
> > ->xfs_ilock->xfs_ilock_ra->mraccessf->lock_wait *hang*
> > xfs_repair 1.2.1 reveals (-n) many errors. I have the damaged
> > filesystem handy for poking around with xfs_db.
> > Kernel is 2.4.3-XFS 2001/04/04 15:42 CEST.
> > Peter