On Sun, May 29, 2005 at 11:29:56AM -0700, Derek Kuli?ski wrote: > Hello, > > Today I noticed following message in the log: > > > KDB: stack backtrace: > > kdb_backtrace(c07163b8,2,c661994c,0,22) at kdb_backtrace+0x2e > > getdirtybuf(d109ebac,0,1,c661994c,1) at getdirtybuf+0x2b > > flush_deplist(c282f4cc,1,d109ebd4,d109ebd8,0) at flush_deplist+0x57 > > flush_inodedep_deps(c15ba800,22a8a,c2760a7c,d109ec34,c04f7f87) at > > flush_inodedep_deps+0x9e > > softdep_sync_metadata(d109eca4,c2760a50,50,c06ea8f0,0) at > > softdep_sync_metadata+0x9d > > ffs_fsync(d109eca4,0,0,0,0) at ffs_fsync+0x4b2 > > fsync(c17ba000,d109ed14,4,d109ed3c,c0515916) at fsync+0x1a1 > > syscall(c069002f,2f,2f,81522b0,81522b0) at syscall+0x370 > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > --- syscall (95, FreeBSD ELF32, fsync), eip = 0x28143dcf, esp = 0xbfbfd34c, > > ebp = 0xbfbfd358 --- > > KDB: stack backtrace: > > kdb_backtrace(c07163b8,2,c6683118,0,22) at kdb_backtrace+0x2e > > getdirtybuf(d1098bac,0,1,c6683118,1) at getdirtybuf+0x2b > > flush_deplist(c282facc,1,d1098bd4,d1098bd8,0) at flush_deplist+0x57 > > flush_inodedep_deps(c15ba800,1e9a4,c24cc974,d1098c34,c04f7f87) at > > flush_inodedep_deps+0x9e > > softdep_sync_metadata(d1098ca4,c24cc948,50,c06ea8f0,0) at > > softdep_sync_metadata+0x9d > > ffs_fsync(d1098ca4,0,0,0,0) at ffs_fsync+0x4b2 > > fsync(c17b9c00,d1098d14,4,c17b9c00,7) at fsync+0x1a1 > > syscall(2f,2f,bfbf002f,8111fe0,0) at syscall+0x370 > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > --- syscall (95, FreeBSD ELF32, fsync), eip = 0x282dfdcf, esp = 0xbfbf9a8c, > > ebp = 0xbfbfb468 --- > > System didn't seem to crash, what does it mean?
It looks like debugging code (it's been removed in -current). Jeff: in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp == NULL..you removed it in current in 1.166, but some people are seeing it trigger on 5.x Kris
pgpdSk4H1tz2r.pgp
Description: PGP signature
