From: Eric Sandeen <sandeen@sandeen.net>
To: 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, 06 Jan 2015 11:02:09 -0600 [thread overview]
Message-ID: <54AC1511.1060908@sandeen.net> (raw)
In-Reply-To: <1806495.BCZcrVVEOf@shtub-cm>
On 1/4/15 6:56 PM, Hillel Lubman wrote:
> Hi.
> 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).
It is indeed the default.
[root@sandeen ~]# blockdev --getss --getpbsz /dev/sde
512
4096
[root@sandeen ~]# mkfs.xfs /dev/sde
meta-data=/dev/sde isize=256 agcount=1, agsize=4097 blks
= sectsz=4096 attr=2, projid32bit=0
data = bsize=4096 blocks=4097, imaxpct=25
= sunit=1 swidth=8 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=1424, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
however, some drives lie about these sizes, and then mkfs.xfs can't know.
Try the blockdev command above to see.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-06 17:02 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
2015-01-06 17:02 ` Eric Sandeen [this message]
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=54AC1511.1060908@sandeen.net \
--to=sandeen@sandeen.net \
--cc=shtetldik@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