Date: Thu, 5 Jan 2006 11:53:24 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: dsh@vlink.ru Cc: freebsd-stable@FreeBSD.org Subject: Re: Recurring problem: processes block accessing UFS file system Message-ID: <200601051953.k05JrOmx015661@gw.catspoiler.org> In-Reply-To: <87bqyqa2dn.fsf@neva.vlink.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 Jan, Denis Shaposhnikov wrote: >>>>>> "Don" == Don Lewis <truckman@FreeBSD.org> writes: > > Don> pid 519 wants to lock this vnode but some other thread is > Don> holding the vnode lock. Unfortunately we don't know who the > Don> lock holder is because the message is truncated. > > Is it possible to find out the answer from the crashdump? It's possible if you have the matching debug kernel, though it is more painful. In kgdb: print *(struct vnode *)0xc691f318 print (struct vnode *)0xc691f318->v_vnlock->lk_lockholder->td_proc->p_pid) or something like that. > Don> This might just be a vnode lock leak. Build a debug kernel with > Don> the DEBUG_VFS_LOCKS and DEBUG_LOCKS options and see if anything > Don> shows up. > > I'll try, thank you. Are you using any unusual file systems, such as nullfs or unionfs?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601051953.k05JrOmx015661>