From: Stan Hoeppner <stan@hardwarefreak.com>
To: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>,
Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: extremely slow file creation/deletion after xfs ran full
Date: Tue, 13 Jan 2015 14:06:37 -0600 [thread overview]
Message-ID: <54B57ACD.60600@hardwarefreak.com> (raw)
In-Reply-To: <54B40552.50106@aei.mpg.de>
On 01/12/2015 11:33 AM, Carsten Aulbert wrote:
...
> The FS was never grown, the machine was installed on November 5th, 2012
> and was (ab)using the FS ever since. On average there have been about
> 1-2 million file creations per day (ranging from a few kByte files to a
> few 100 kBytes) and also an equally large number of deletions (after
> some time). Thus overall, a somewhat busy server.
This workload seems more suited to a database than a filesystem. Though
surely you've already considered such, and chose not to go that route.
With high fragmentation you get lots of seeking. What model disks are
these? What is your RAID10 geometry? Are your partitions properly
aligned to that geometry, and to the drives (512n/512e)?
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-13 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 8:36 extremely slow file creation/deletion after xfs ran full Carsten Aulbert
2015-01-12 12:44 ` Brian Foster
2015-01-12 13:30 ` Carsten Aulbert
2015-01-12 15:52 ` Brian Foster
2015-01-12 16:09 ` Carsten Aulbert
2015-01-12 16:37 ` Brian Foster
2015-01-12 17:33 ` Carsten Aulbert
2015-01-13 20:06 ` Stan Hoeppner [this message]
2015-01-13 20:13 ` Carsten Aulbert
2015-01-13 20:43 ` Stan Hoeppner
2015-01-14 6:07 ` Carsten Aulbert
2015-01-13 20:33 ` Dave Chinner
2015-01-14 6:12 ` Carsten Aulbert
2015-01-16 15:35 ` Carlos Maiolino
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=54B57ACD.60600@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=Carsten.Aulbert@aei.mpg.de \
--cc=bfoster@redhat.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