public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dave Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org, g.danti@assyoma.it
Subject: Re: XFS and sector size on thin volumes
Date: Sat, 16 Sep 2017 21:59:27 +0200	[thread overview]
Message-ID: <58a80905e97216e37d72e5b7bd9f1643@assyoma.it> (raw)
In-Reply-To: <4ca74023-dcaf-9963-1b8f-2c1924866564@sandeen.net>

Il 16-09-2017 20:33 Eric Sandeen ha scritto:
> 
> I don't think I said that - this is the first time you've mentioned
> /alignment/, and I've seen no indication of your alignment one way or
> another.
> 
> 
> 
> 
> that specifies a 4k block size, which is already the default.
> 
> You're conflating a lot of issues here - log alignment, sector size,
> physical & logical block size presented by both the underlying
> storage and the zvol ...
> 
> I cannot speak to zvols, as I have no experience with them.
> 
> But if the underlying storage is 512e/4k then you may want to specify
> the 4k /sector/ size with -s size=4k.
> 
> -Eric
> 

Hi Eric, you are right: I messed up the terminology. Sorry for the 
noise.

I was really speaking about *sector* size. In short, when using ZVOL the 
physical disk's sector size is not directly announced to the higher 
layer filesystem. This, in turn, cause mkfs.xfs to automatically select 
a 512B sector size, even when running on top of 512e/4Kn disks.

 From previous emails/threads, I was under impression that XFS sector 
size only very marginally affect performance. It that true? Can I stick 
with default mkfs settings? Or should I manually select 4K sector size 
("-s size=4k")?

Thanks.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2017-09-16 19:59 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
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 [this message]
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=58a80905e97216e37d72e5b7bd9f1643@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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