From: Eric Sandeen <sandeen@sandeen.net>
To: Hillel Lubman <shtetldik@gmail.com>
Cc: 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 23:30:26 -0600 [thread overview]
Message-ID: <54ACC472.4010104@sandeen.net> (raw)
In-Reply-To: <2511571.nTXGg0tW6M@shtub-cm>
On 1/6/15 11:17 PM, Hillel Lubman wrote:
> I see. Indeed, on the drive where I get sectsz as 512 by default, blockdev --getss --getpbsz reports:
>
> 512
> 512
what kind of drive is this; is it usb, SATA, or ?
> However hdparm -I reports:
>
> Logical Sector size: 512 bytes
>
> Physical Sector size: 4096 bytes
>
> So is it still worthwhile making sectsz 4 KB explicitly instead of
> using mkfs.xfs default in such case? And on a side note, since there
> is a more reliable way to figure that info out, may be mkfs.xfs
> should rather use that?
>
a) probably can't hurt
b) probably doesn't matter ;)
c) not sure why there are 2 different answers. Knowing what kind of drive
it is would be good; mkfs.xfs just uses whatever blkid says.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-07 5:30 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
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 [this message]
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=54ACC472.4010104@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.