From: Stefan Priebe <s.priebe@profihost.ag>
To: stan@hardwarefreak.com
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: suddenly slow writes on XFS Filesystem
Date: Mon, 07 May 2012 22:05:27 +0200 [thread overview]
Message-ID: <4FA82B07.1020102@profihost.ag> (raw)
In-Reply-To: <4FA7FA14.6080700@hardwarefreak.com>
Am 07.05.2012 18:36, schrieb Stan Hoeppner:
> This shows what I originally suspected. Notice how top heavy this
> histogram is. Over half of your free space sits on little islands of
> 8MB or less. 17% is in islands of 60KB or less. This is heavily
> fragmented free space. Contrast this with an XFS from the opposite end
> of the aging spectrum that is only 1/3rd full and has seen very few
> deletes as it has aged:
...
>
> Notice how it is very bottom heavy, and that 85% of the free space is in
> large islands of 16GB to 24GB.
This totally makes sense too me. Thanks for this explanation.
> Stefan, at this point in your filesystem's aging process, it may not
> matter how much space you keep freeing up, as your deletion of small
> files simply adds more heavily fragmented free space to the pool. It's
> the nature of your workload causing this.
This makes sense - do you have any idea or solution for this? Are
Filesystems, Block layers or something else which suits this problem /
situation?
> What I would suggest is doing an xfsdump to a filesystem on another LUN
> or machine, expand the size of this LUN by 50% or more (I gather this is
> an external RAID), format it appropriately, then xfsrestore. This will
> eliminate your current free space fragmentation, and the 50% size
> increase will delay the next occurrence of this problem. If you can't
> expand the LUN, simply do the xfsdump/format/xfsrestore, which will give
> you contiguous free space.
But this will only help for a few month or perhaps a year.
Greets,
Stefan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-07 20:05 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
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 [this message]
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=4FA82B07.1020102@profihost.ag \
--to=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