From: Dave Chinner <david@fromorbit.com>
To: Alphazo <alphazo@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: finobt option for end user
Date: Mon, 22 Dec 2014 09:18:53 +1100 [thread overview]
Message-ID: <20141221221853.GG24183@dastard> (raw)
In-Reply-To: <CAHJqNbx8qrs6OosFq1TGz4jqzxh82zvLRzxQ1oWpOp5MP6h3oQ@mail.gmail.com>
On Sat, Dec 20, 2014 at 11:52:57PM +0100, Alphazo wrote:
> Hello,
>
> I'm pretty new to XFS. I'm considering moving away from ext4 to XFS because
> of the new self-describing option, performance and reliability improvements
> that XFS went through over the past year. Now I'm puzzled with the new free
> inode btree option (finobt). I tried to find some documentation about it
> but couldn't find the pros or cons. So from an end-user perspective with a
> couple of TB worth of photos:
> - Does it improve overall reliability?
No effect on reliability, good or bad.
> - Does it provide faster fsck/repair?
No, if anything, it slows it down because there's more metadata to
verify and rebuild.
> - Does it improve any read or write operation?
No.
> - Is it safe to use and does it recover as well as with finobt=0?
Yes and yes.
> - What is the typical case for enabling it
It improves performance on aged filesystems i.e. months or years
down the track when you've added and removed millions of
files to/from the filesystem.
> and would you recommend using it
> for any new fs creation?
Consider the fact that "-m crc=1,finobt=1" will be made the mkfs
default in 3-6 months time - that will probably co-incide with a
xfsprogs 3.3 release....
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:[~2014-12-21 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 22:52 finobt option for end user Alphazo
2014-12-21 20:38 ` Michael L. Semon
2014-12-21 21:30 ` Alphazo
2014-12-21 22:18 ` Dave Chinner [this message]
2014-12-23 22:35 ` Alphazo
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=20141221221853.GG24183@dastard \
--to=david@fromorbit.com \
--cc=alphazo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox