> When i was stresstesting my UDF again with multiple processes accessing the 
> same directorytree simultaniously while transfering heaps of data from it 
> and printing heaps of data on the console while in the background a 
> compilation job was running, the copier suddenly got stuck on [vnode] and 
> all the other UDF accessing processes got stuck on the node translation 
> lock i inserted. Thus that can only mean that vget(vp, LK_EXCLUSIVE | 
> LK_INTERLOCK) got stuck in this or getnewvnode(). Could this be a sheduler 
> induced lock conflict? like recently seen on ftp.n.o ?

what do you mean by "a scheduler induced lock conflict" ?
do you mean "a bug in scheduler"?  if so, why do you think so?

if i were you, i'd try to reproduce the problem on
other filesystems like ffs. :)

YAMAMOTO Takashi