From: Dave Chinner <david@fromorbit.com>
To: Pippin Wallace <nippip@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Looking to confirm issue and seek advice on fix for inode btree fragmentation
Date: Fri, 14 Aug 2015 10:03:03 +1000 [thread overview]
Message-ID: <20150814000303.GR3902@dastard> (raw)
In-Reply-To: <CA+muJ0thea8xOJB8c2CJj1GAVa48EUvRYf7-3oS_zYc+T5R6yg@mail.gmail.com>
On Thu, Aug 13, 2015 at 05:35:31PM -0600, Pippin Wallace wrote:
> I am writing to confirm the issue I think I have and get advice on the best
> short term and long term “fixes”.
>
>
>
> In reading the following threads and others I am pretty sure I have inode
> btree fragmentation and I have included detailed output below to help
> confirm this.
Make a new filesystem with a current xfsprogs 3.2.4, and it will use
the new free inode btree for allocation that was designed to avoid
this problem.
> Long term fix is upgrade kernel to >= 3.16, xfsprogs >=3.2.1 and rebuild fs
> with new finobt structure.
>
> # mkfs.xfs -m crc=1,finobt=1 <dev>
i.e. there are the default mkfs options in xfsprogs >= 3.2.3.
It's really the only viable fix, especially given that you can't use
inode64. And, realistically, it's still going to cause problems
unless you ensure that you have smaller-than-default AGs (e.g. 250GB
AGs) so that there are multiple inode btrees in the 32-bit inode
number region of the filesystem.(*)
(*) which is actually the first 2TB of the filesystem with CRC
enabled filesystems because the inode size is 512 bytes...
> *KERNEL OPTIONS: Which of these kernels should I choose for the best XFS
> support for this issue?*
One your distro vendor supports; the newer the better.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-08-14 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 23:35 Looking to confirm issue and seek advice on fix for inode btree fragmentation Pippin Wallace
2015-08-14 0:03 ` Dave Chinner [this message]
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=20150814000303.GR3902@dastard \
--to=david@fromorbit.com \
--cc=nippip@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.