I'll also point out that you are very likely to see this error when your NFS server is using ext3. ext3 is helluva slow, and the Linux kernel will sometimes just stall for 40-60 seconds while it thinks about what it's going to do to the fs. It sucks. Real bad. When the thing stalls, no local proccesses get CPU time (whether they're reading from that disk or not), and no network IO happens. The box just sits. It happens a lot when you're opening many files or just stat()ing many files in succession.
I'm not seeing this on 2.4.20-13.7smp (RH 7.3).
ext2 doesn't have that problem. The problem becomes much less significant on ext3 if you mount the fs using the "noatime" option.
That could be why. I do have fs mounted noatime.
YMMV, jerry
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
