Andreas Aardal Hanssen wrote:
> So you stopped Binc while it was committing flag updates to the mailbox
> after as the final step of STORE. If this is really where Binc is
> spinning, then it's got to be the readdir() libc call. The loop Binc is in
> starts at the beginning of a directory and continues to the end.
Is there some way binc might be following '..'? Because our NetApp filer acts like someone is doing a 'find / -print' when binc is hung up like this.
> I find it interesting that you're running Binc over NFS; but..
We've got a nice NetApp filer that provides all sorts of nice service. And that is where everyone's home directories are. It actually works nicely, and that way I have all the RAID protection the NetApp provides us.
> Let's see what we can do. I'm going to have to ask for another trace, this
> time with strace. If you find a haywire Binc process, first verify that
> it's bincimap-up or bincimapd that is spinning. Then attach to the haywire
> process like this:
[procedure to do new trace deleted]
> Meanwhile, I'm looking up all docs I can find about NFS and problems with > readdir(). :-/
Thanks, --Kurt
