public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Hillel Lubman <shtetldik@gmail.com>, xfs@oss.sgi.com
Subject: Re: What is a recommended XFS sector size for hybrid (512e) advanced format hard drives?
Date: Tue, 6 Jan 2015 09:35:07 +0100	[thread overview]
Message-ID: <20150106083507.GA9943@citd.de> (raw)
In-Reply-To: <54AA0A93.2010204@hardwarefreak.com>

On 04.01.2015 21:52, Stan Hoeppner wrote:
> On 01/04/2015 06:56 PM, Hillel Lubman wrote:
> ...
> > Looking around I saw some references that it's preferable to use sector
> > size (sectsz) of 4 KB when creating XFS partitions on hybrid (512e)
> > advanced format hard drives and also some mentions of making that a
> > default in mkfs.xfs. However I noticed that my current mkfs.xfs (3.2.1)
> > used with current Debian testing (Linux 3.16.0) still uses 512 B sectors
> > by default.
> ...
> > Can you please clarify what after all is the recommended sector size for
> > such drives and why isn't it a default in mkfs.xfs (since supposedly
> > defaults are generally recommended optimal settings unless you have some
> > special use case).
> ...
> 
> XFS sectsz is unimportant with these drives.  What matters is that any
> partitions you create start and end on 4KB boundaries.  This will
> prevent adjacent hardware sector RMW internal to the drive.  XFS writes
> in 4KB filesystem blocks on Linux.  As long as the fsblocks are aligned
> to the 4KB hardware sectors there's nothing more you can do to avoid
> performance penalties with these drives.

Not in my experience. My first (and lying about it) AF HDD had horrible 
write performance until i re'mkfs.xfs'ed it with 4k sector-size. And yes 
the aligned was 4k.

But that was many years ago and i don't know if newer XFS (IIRC that was 
before delay-log) would behave better. But as all of my storage after 
the first AF HDD was either an AF HDD or a SSD i have been formating 
everything with 4k sector-size for years.




-- 

Matthias

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2015-01-06  8:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  0:56 What is a recommended XFS sector size for hybrid (512e) advanced format hard drives? Hillel Lubman
2015-01-05  3:52 ` Stan Hoeppner
2015-01-06  2:23   ` Hillel Lubman
2015-01-06  3:21     ` Stan Hoeppner
2015-01-06  4:01       ` Hillel Lubman
2015-01-06  8:35   ` Matthias Schniedermeyer [this message]
2015-01-06 17:02 ` Eric Sandeen
2015-01-06 19:05   ` Chris Murphy
2015-01-06 19:23     ` Eric Sandeen
2015-01-06 19:42       ` Chris Murphy
2015-01-06 19:55         ` Chris Murphy
2015-01-07  5:31           ` Eric Sandeen
2015-01-07  6:01             ` Chris Murphy
2015-01-07  5:17   ` Hillel Lubman
2015-01-07  5:30     ` Eric Sandeen
2015-01-07  5:36       ` Hillel Lubman
2015-01-07  6:06         ` Chris Murphy

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=20150106083507.GA9943@citd.de \
    --to=ms@citd.de \
    --cc=shtetldik@gmail.com \
    --cc=stan@hardwarefreak.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