Thanks Brian. I tried what you recommended. At first I was very encouraged when I saw things moving across the wire. But about 15 minutes into the transfer things ground to a halt. I am currently running across a GigE channel. Things were moving about 20-40 MB/s but when things stopped moving the transfer rate is down in single digit kb/s. Even doing a top level directory listing takes quite a while. <div>
<br></div><div>Not in a happy state.</div><div><br><br><div class="gmail_quote">On Mon, Nov 5, 2012 at 10:10 AM, Brian Candler <span dir="ltr"><<a href="mailto:B.Candler@pobox.com" target="_blank">B.Candler@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If your disks are >1TB with XFS then try mount -o inode64<br>
<br>
This has the effect of sequential writes into the same directory being<br>
localised next to each other (within the same allocation group). When you<br>
skip to the next directory you will probably get a different allocation<br>
group.<br>
<br>
Without this, the behaviour is to (a) stick all the inodes in the first<br>
allocation group, and (b) to stick every file into a random allocation<br>
group, regardless of the parent directory<br>
</blockquote></div><br><br clear="all"><div><br></div>
</div>