[Gluster-users] Very slow directory listing and high CPU usage on replicated volume

Jonathan Lefman jonathan.lefman at essess.com
Mon Nov 5 18:10:40 UTC 2012

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.

Not in a happy state.

On Mon, Nov 5, 2012 at 10:10 AM, Brian Candler <B.Candler at pobox.com> wrote:

> If your disks are >1TB with XFS then try mount -o inode64
> This has the effect of sequential writes into the same directory being
> localised next to each other (within the same allocation group). When you
> skip to the next directory you will probably get a different allocation
> group.
> Without this, the behaviour is to (a) stick all the inodes in the first
> allocation group, and (b) to stick every file into a random allocation
> group, regardless of the parent directory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121105/2ce3508c/attachment.html>

More information about the Gluster-users mailing list