Dave,
futex comes from doing a simple strace, which showed the futex as the call that was being blocked. My fear is that it is a holdover from an old, dead process; we went through each process on the system and lsof -p'd it, didn't see anything.
Thanks for the suggestion of sysrq btw, I'll try that the next time I have access to the box, but waiting doesn't help.Also, I don't see in sysrq the actual ability to *kill* wayward locks however; but it will a great help us track down the underlying issue.
futex comes from doing a simple strace, which showed the futex as the call that was being blocked. My fear is that it is a holdover from an old, dead process; we went through each process on the system and lsof -p'd it, didn't see anything.
Thanks for the suggestion of sysrq btw, I'll try that the next time I have access to the box, but waiting doesn't help.Also, I don't see in sysrq the actual ability to *kill* wayward locks however; but it will a great help us track down the underlying issue.
Thanks,
Ed
Ed
The one thing I don't see in sysrq is a way to
As for sys
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
