On Thursday, 5 February 2004 at 15:40:06 -0800, David Benfell wrote: > Hello all, > > I've been getting these messages on my console and in my kernel log. > I'm noticing stuff in there that looks like it has to do with the > filesystem. Both the disks on this system are IDE disks, so yes, this > kind of gets my attention.
>> syscall(2f,2f,2f,bfbfee14,bfbfedc3) at syscall+0x217 >> Xint0x80_syscall() at Xint0x80_syscall+0x1d >> --- syscall (95), eip = 0x280b8677, esp = 0xbfbfed9c, ebp = 0xbfbfedcc --- >> Stack backtrace: >> backtrace(c25d0f00,1,cda99c14,cda99c00,c0718580) at backtrace+0x12 >> getdirtybuf(cda99bf0,0,1,c45b52a8,1) at getdirtybuf+0x2c >> flush_deplist(c2c27a4c,1,cda99c14) at flush_deplist+0x30 >> flush_inodedep_deps(c217b000,285eb,c087f118,cda99c60,c05fb1e0) at >> flush_inodedep_deps+0x82 >> softdep_sync_metadata(cda99cb0) at softdep_sync_metadata+0x72 >> ffs_fsync(cda99cb0) at ffs_fsync+0x336 >> fsync(c23f37e0,cda99d14,1,1,292) at fsync+0x10b >> syscall(2f,2f,2f,bfbfee14,bfbfedc3) at syscall+0x217 >> Xint0x80_syscall() at Xint0x80_syscall+0x1d > What does it mean? I'm running 5.2-CURRENT on this system: If you're running -CURRENT, you should be following the FreeBSD-current list and be prepared to look for the problems yourself. -questions is the wrong mailing list for this. Looking at getdirtybuf(), we see: if (bp->b_vp == NULL) backtrace(); In other words, getdirtybuf() has been passed a corrupt buffer header. This is almost certainly a bug. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers.
pgp00000.pgp
Description: PGP signature