From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: stan@hardwarefreak.com, xfs@oss.sgi.com
Subject: Re: suddenly slow writes on XFS Filesystem
Date: Mon, 7 May 2012 11:39:40 +1000 [thread overview]
Message-ID: <20120507013940.GX5091@dastard> (raw)
In-Reply-To: <4FA6D016.6010702@profihost.ag>
On Sun, May 06, 2012 at 09:25:10PM +0200, Stefan Priebe wrote:
> Am 06.05.2012 17:45, schrieb Stan Hoeppner:
> >On 5/6/2012 5:33 AM, Martin Steigerwald wrote:
> >>Am Sonntag, 6. Mai 2012 schrieb Stefan Priebe:
> >>>It is a raid 10 of 20 SATA Disks and i can only write to them with
> >>>about 700kb/s while doing random i/o. I tried vanilla Kernel 3.0.30
> >>>and 3.3.4 - no difference. Writing to another partition on another xfs
> >>>array works fine.
> >>
> >>Additionally what RAID is this? SoftRAID or some - which one? - hardware
> >>RAID controller? And what disks are used, whats the rpm of these?
> >
> >I doubt much of this stuff matters. Stefan's filesystem is 96% full,
> >w/~200GB free. This free space is likely heavily fragmented. If he's
> >doing allocation in this fragmented free space I'd think that would
> >fully explain his write performance dropping off a cliff due to massive
> >head seeking.
> >
> Thanks Stan that's it. After deleting 200GB-300GB it's running fine again.
>
> What is the general recommandation of free space?
Depends on the size of the filesystem. If you've got a 500TB
filesystem, then running at 98% full (10TB of free space) is not
going to be a big deal. But running at 98% full on a 5TB volume is a
big deal because there is relatively little freespace per AG and it
will get rapidly fragmented.
So for a 5TB volume, I' say don't run sustained operations at over
90% full. Going above this temporarily won't be a problem, but
staying at >95% full will definitely cause accelerated aging of the
filesystem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-07 1:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 9:01 suddenly slow writes on XFS Filesystem Stefan Priebe
2012-05-06 10:31 ` Martin Steigerwald
2012-05-06 10:33 ` Martin Steigerwald
2012-05-06 15:45 ` Stan Hoeppner
2012-05-06 19:25 ` Stefan Priebe
2012-05-07 1:39 ` Dave Chinner [this message]
2012-05-06 21:43 ` Martin Steigerwald
2012-05-07 6:40 ` Stefan Priebe - Profihost AG
2012-05-07 1:34 ` Dave Chinner
2012-05-07 6:39 ` Stefan Priebe - Profihost AG
2012-05-07 7:17 ` Dave Chinner
2012-05-07 7:22 ` Stefan Priebe - Profihost AG
2012-05-07 16:36 ` Stan Hoeppner
2012-05-07 19:08 ` Martin Steigerwald
2012-05-07 20:05 ` Stefan Priebe
2012-05-09 6:57 ` Stan Hoeppner
2012-05-09 7:04 ` Dave Chinner
2012-05-09 7:36 ` Stefan Priebe - Profihost AG
2012-05-09 7:49 ` Stan Hoeppner
2013-02-15 15:06 ` 32bit apps and inode64 Stefan Priebe - Profihost AG
2013-02-15 21:46 ` Ben Myers
2013-02-16 10:24 ` Stefan Priebe - Profihost AG
2013-02-17 21:33 ` Dave Chinner
2013-02-18 8:12 ` Stefan Priebe - Profihost AG
2013-02-18 22:06 ` Dave Chinner
2013-02-17 8:13 ` Jeff Liu
2013-02-19 19:11 ` Ben Myers
2012-05-07 23:42 ` suddenly slow writes on XFS Filesystem Dave Chinner
2012-05-07 8:21 ` Martin Steigerwald
2012-05-07 16:44 ` Stan Hoeppner
2012-05-07 8:31 ` Martin Steigerwald
2012-05-07 13:57 ` Stefan Priebe - Profihost AG
2012-05-07 14:32 ` Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120507013940.GX5091@dastard \
--to=david@fromorbit.com \
--cc=s.priebe@profihost.ag \
--cc=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox