Have you run oprofile on the client and server simultaneously to see if there's some race condition developing? Obviously the NFS client is fine, but it's clear that there's nothing wrong with the hardware. oprofile will at least reveal where the the bits are vacationing and may point a specific bottleneck. oprofile.sf.net for docs and examples (pretty good); fairly easy to set up to profile applications; a bit more trouble if you're trying to profile kernel interactions, but it looks like you might not have to. I wouldn't want to forklift 160TB either. My sympathies. hjm On Thursday, March 07, 2013 09:27:42 PM Thomas Wakefield wrote: > inode size is 256. > > Pretty stuck with these settings and ext4. I missed the memo that Gluster > started to prefer xfs, back in the 2.x days xfs was not the preferred > filesystem. At this point it's a 340TB filesystem with 160TB used. I just > added more space, and was doing some followup testing and wasn't impressed > with the results. But I am sure I was happier before with the performance. > > Still running CentOS 5.8 > > Anything else I could look at? > > Thanks, Tom <...> --- Harry Mangalam - Research Computing, OIT, Rm 225 MSTB, UC Irvine [m/c 2225] / 92697 Google Voice Multiplexer: (949) 478-4487 415 South Circle View Dr, Irvine, CA, 92697 [shipping] MSTB Lat/Long: (33.642025,-117.844414) (paste into Google Maps) ---
