xfs
[Top] [All Lists]

Re: Issues and new to the group

To: Ronnie Tartar <rtartar@xxxxxxxxxxxx>
Subject: Re: Issues and new to the group
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Thu, 26 Sep 2013 07:06:37 -0500
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <0e4201cebaae$24873680$6d95a380$@host2max.com>
References: <0e4201cebaae$24873680$6d95a380$@host2max.com>
Reply-to: stan@xxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
On 9/26/2013 6:47 AM, Ronnie Tartar wrote:

> I have a 600GB xfs file system mounted that suddenly started running slow on
> writes.  It takes about 2.5 to 3.5 seconds to write a single file.  Some

This typically occurs when the filesystem gets near full and free space
is heavily fragmented.  Writing to these free space fragments requires
lots of seeking.  Seeking causes latency.  I assume your storage device
is spinning rust, yes?

> folders (with less number of files) work well.  But it will copy fast, then
> slow for long periods of time.  

Some allocation groups may have less fragmented free space than others.
 Put another way, they may have more contiguous free space.  Thus less
seeking.

> This is a virtualized CentOS 5.9 64 bit box
> on Citrix Xenserver 5.6SP2.  Doesn't seem to be a load i/o issue as most of
> the load is system%.  My fragmentation is less than 1 %.    Any help would
> be greatly appreciated.  I was looking to see if there was a better way to
> mount this partition or allocate more memory, whatever it takes.  The
> folders are image folders that have anywhere between 5 to 10 million images
> in each folder.

> Fstab mount is: 
> /dev/xvdb1              /images xfs
> defaults,nodiratime,nosuid,nodev,allocsize=64m 1 1
                                   ^^^^^^^^^^^^^
This tells XFS to allocate 64MB of free space at the end of each file
being allocated.  If free space is heavily fragmented and the fragments
are all small, this will exacerbate the seek problem.  Given the 64MB
allocsize, I assume these image files are quite large.  If this is
correct, writing them over scattered small free space fragments also
requires seeking.  Thus, I'd guess you're seeking your disk, or array,
to death.

How full is the XFS volume, and what does your free space fragmentation
map look like?

-- 
Stan

<Prev in Thread] Current Thread [Next in Thread>