Re: 6.0-BETA: locked in lockmgr for fsync

On Thursday 31 August 2006 09:17, Bjoern A. Zeeb wrote:
> Hi,
> 
> this was on a 6.0-BETA machine in case anyone is interested.
> Quick grepping didn't show me the same trace though there
> were similiar looking once.
> The machine was hanging completly, breaking to kernel debugger
> was the only thing I could do. No debugging of locks though
> so no show alllocks.
> 
> lockmgr(c6603d90,200012,0,c16b6600) at lockmgr+0x4
> getdirtybuf(c6603d30,c0979ce0,1,4,1) at getdirtybuf+0x6b
> flush_deplist(c16d004c,1,d0a6ec08) at flush_deplist+0x30
> flush_inodedep_deps(c16ea000,4091,0,0,c6642200) at flush_inodedep_deps+0xcf
> softdep_sync_metadata(c2501440) at softdep_sync_metadata+0x61
> ffs_syncvnode(c2501440,1,c2649dec,d0a6ec94,c083ee4c) at ffs_syncvnode+0x3a3
> ffs_fsync(d0a6ecc0) at ffs_fsync+0x12
> VOP_FSYNC_APV(c09330c0,d0a6ecc0) at VOP_FSYNC_APV+0x38
> fsync(c16b6600,d0a6ed04,1,46fe,296) at fsync+0x170
> syscall(bfbf003b,805003b,bfbf003b,40,8056800) at syscall+0x2b3
> Xint0x80_syscall() at Xint0x80_syscall+0x1f
> --- syscall (95, FreeBSD ELF32, fsync), eip = 0x280c8f87, esp = 0xbfbfdb1c, 
ebp = 0xbfbfee38 ---

Do you have a coredump?

-- 
John Baldwin