From: Dave Chinner <david@fromorbit.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS and sector size on thin volumes
Date: Sun, 10 Sep 2017 09:12:15 +1000 [thread overview]
Message-ID: <20170909231215.GK17782@dastard> (raw)
In-Reply-To: <d95f09118ee6cb2fe0562ad35303715c@assyoma.it>
On Sun, Sep 10, 2017 at 12:11:56AM +0200, Gionatan Danti wrote:
> Hi all,
> I noticed that, when using both LVM thin volumes and ZVOLs, mkfs.xfs
> default to using 512-byte sector size.
>
> Would setting sector size to 4K be benefical for filesystem performance?
Probably not. And, worse, you open up the possibility of torn
"single sector" writes if the underlying device isn't a native 4k
sector device.
> From what I know, sector size only affect journal and metadata
> writes. So, should I manually set sector size to 4K or it is not
> worth the (minor) inconvenience?
Only the log might matter for performance, the AG headers are only
read at mount and rarely written because they are so frequently
logged. But, really, the difference between 512 byte and 4k sectors
for the log is going to be pretty damn small. Just use the defaults
and only consider changing them if you observe problems...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-09-09 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 22:11 XFS and sector size on thin volumes Gionatan Danti
2017-09-09 23:12 ` Dave Chinner [this message]
2017-09-09 23:26 ` Gionatan Danti
2017-09-09 23:53 ` Dave Chinner
2017-09-11 22:14 ` Gionatan Danti
2017-09-11 22:28 ` Eric Sandeen
2017-09-12 5:24 ` Gionatan Danti
2017-09-16 16:43 ` Gionatan Danti
2017-09-16 18:33 ` Eric Sandeen
2017-09-16 19:59 ` Gionatan Danti
2017-09-16 22:01 ` Eric Sandeen
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=20170909231215.GK17782@dastard \
--to=david@fromorbit.com \
--cc=g.danti@assyoma.it \
--cc=linux-xfs@vger.kernel.org \
/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