Re: Well, I agree in theory but...
> Since nfs-kernel-server isn't kind enough to proved a human parsable entry in /proc to let you know which instance of nfsd is actually holding a given file (and since each nfsd process doesn't map 1:1 to a particular nfs export that wouldn't help even if they did) there's no way to know which instance you can kill to get your lock back.
This sounds like something you could fix right quick, if you had the source code.
Biting the hand that feeds IT
