<html><head/><body><html><head></head><body>I would also watch cpu and memory usage. Maybe try the deadline scheduler. Monitor your switch. Since it works fine at first, look for what changes.<br><br><div class="gmail_quote">Brian Candler <B.Candler@pobox.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">On Mon, Nov 05, 2012 at 01:10:40PM -0500, Jonathan Lefman wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Thanks Brian. I tried what you recommended. At first I was very<br />encouraged when I saw things moving across the wire. But about 15<br />minutes into the transfer things ground to a halt. I am currently<br />running across a GigE channel. Things were moving about 20-40 MB/s but<br />when things stopped moving the transfer rate is down in single digit<br />kb/s. Even doing a top level directory listing takes quite a while.</blockquote><br />Hmm. Maybe an strace on the client side (glusterfs FUSE process) and server<br />side (glusterfsd) might give some clues?<br /><hr /><br />Gluster-users mailing list<br />Gluster-users@gluster.org<br /><a
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br /></pre></blockquote></div></body></html></body></html>