Mike Polek wrote:
First, I'd like to start out by saying that since getting some serious (paid for) support from Jeff Altman last year for our Windows client woes (well ... more like photoshop woes, but they weren't interested in fixing the issue), our end-user complaints for Windows systems has gone to near zero. Best $$ I ever spent on software support. ;-) Thanks Jeff.I currently have an end user claiming that if he does a lot of very heavy I/O for a couple days, his client will lock up. I have not yet observed this myself. I just became aware of it. He's been restarting the client on his own.
If you can get the user to "fs minidump" when the lockup occurs that would be very helpful.
Of course, if the user isn't running the most recent client upgrading is the first thing that should be done. The current release is 1.5.33.
Checking the RX stats for the machines in question, I note that the "noPackets" count is non-zero... and I'm curious if there is some RX tuning that needs to be done to give the client more network resources to deal with the heavy traffic. I recently posted about an issue I was having with the linux client, and increasing the number of preallocated RX packets solved my bottleneck issue there.
Funny thing you should ask about Rx configuration 1.5.33 adds two functions: 1. it turns on Rx Hot Thread support which significantly improves the ability of the client to read incoming Rx packets off the wire without dropping them. 2. it adds the "RxExtraPackets" registry value which performs exactly the same function that the command line option does on UNIX.
I looked in the "Advanced" tab for client configuration, but didn't see anything that looked like it could be adjusted in a way that would help me out. Any ideas/tips/pointers?
The Client Configuration tool has not been updated with any of the new knobs that have been added to the Windows client since I started working on it. I want to completely re-implement the configuration management as a MMC add-on. See http://www.secure-endpoints.com/openafs-windows-roadmap.html for mock-ups of what I want to build. Anyone with cash burning a hole in their pocket is welcome to fund the work.
Instead you need to read the release notes and review the registry options in Appendix A.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
