On Wed, Jun 4, 2008 at 3:45 PM, Ricardo Labiaga <labiaga@xxxxxxxxx> wrote: > Does /var/log/messages show any errors around the same time? In addition to the network trace and rpcdebug on the client, take a look at "nfsstat -d" on the filer. Is the filer dropping the connection? Look for "dropped with EAGAIN" or "dropped from vol offline" in the output. This will help narrow down the problem. So, sometimes when somebody deletes a lot of data (like the problem we just observed), the deleting host, and often other hosts, do report 'filer not responding' in the logs. However, operations that aren't happening in the delete dir, tend to work just fine (for example, iozone could be running and doing pretty well)). Further, the most recent time this happened, the host didn't report filer not responding. This is the only EAGAN reference I see: assist queue (queued, split mbufs, drop for EAGAIN) = (0, 64478612, 94340) Dave ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
