From: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: extremely slow file creation/deletion after xfs ran full
Date: Wed, 14 Jan 2015 07:12:55 +0100 [thread overview]
Message-ID: <54B608E7.9040702@aei.mpg.de> (raw)
In-Reply-To: <20150113203332.GD29484@destitution>
Hi Dave
On 01/13/2015 09:33 PM, Dave Chinner wrote:
>
> This pattern seems to match a filesystem that was running under
> inode32 for most of it's life, and is now using inode64 and hence
> spreading the subdirectories and hence new inodes over all AGs
> instead of just limiting them to AG 0....
>
I fear you are right. The install logs from 2012 show, that fstab simply
contained:
UUID=dd407af5-1edc-41de-8c72-5fe1de31fb11 /srv xfs rw 0 2
And our change management is not that good to track back, when we
changed to inode64.
OK, I think I've gathered quite a lot of things we did wrong. I'll try
to summarize it in another email later today or tomorrow to invite a few
more comments before we go ahead redoing the FS. Also, it may serve as
summary for the list archive.
For now, I want to say a very, very big thank you for remarks and
suggestions!
Cheers
Carsten
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-14 6:13 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
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 [this message]
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=54B608E7.9040702@aei.mpg.de \
--to=carsten.aulbert@aei.mpg.de \
--cc=david@fromorbit.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