[Lustre-discuss] LBUG on client: Found existing inode ... in lock

[Troy Benjegerdes]

> > If I file it (as non-private) maybe it will be closed as duplicate, but
> > actually it would be usefull to keep it around and at least synchronize the
> > status with that of the private bug.
> 
> Yes.  If you were to file it and make it public and note that you were
> told it was an instance of the private bug, while we don't have any
> official policies on what would happen, we could try to at least provide
> some linkage between them.
> 
> > This way people can at least find out
> > what's hapenning and find the non-secret error message.
> 
> Indeed.

I would like to see a policy that all private bugs have a public
duplicate, even if it's just a bug number and a status.