Subject: Re: panic: lockmgr: release of unlocked lock
To: None <firstname.lastname@example.org>
From: YAMAMOTO Takashi <email@example.com>
Date: 01/24/2005 09:19:35
> > > > Just before the panic there is:
> > > > vnode: table is full - increase kern.maxvnodes or NVNODE
> > > >
> > > > I don't know if it's related or not.
> > >
> > > It might be. Please also put a diagnostic printf() near line 473 of
> > > layerfs_lookup(), in the if (error) case just after layer_node_create().
> > > There may be an inconsistency in how we handle an error in case that
> > > create fails.
> > What kind of diagnostic do you have in mind ? I'm sorry, but I don't know
> > this part of the code so I don't know what to check ...
> cnp->cn_flags would be good. Plus the simple fact of the printf happening
> would help too. :-)
> Somehow or another a parent directory is getting returned in the wrong
> lock state. I'm not sure why...
isn't this a known problem?