From: Eric Sandeen <sandeen@sandeen.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: "xfs@oss.sgi.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 13:23:42 -0600 [thread overview]
Message-ID: <54AC363E.1090109@sandeen.net> (raw)
In-Reply-To: <CAJCQCtQqseJ_75WSjqqNMmSjYW-0-L_cWBDDECRVOkiTmHLeVA@mail.gmail.com>
On 1/6/15 1:05 PM, Chris Murphy wrote:
> On Tue, Jan 6, 2015 at 10:02 AM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> however, some drives lie about these sizes, and then mkfs.xfs can't know.
>> Try the blockdev command above to see.
>
> blockdev and parted seem to get this wrong for a device for which
> smartctl and hdparm get correct
I don't think they get it wrong, they are just reporting what the
drive says over that interface.
I ... don't actually know where smartctl/hdparm get the values, vs.
the values exported to blockdev. Is the drive reporting different
values over different query interfaces? Hrm.
mkfs.xfs uses the same interface as used by blockdev.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-06 19:23 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 [this message]
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=54AC363E.1090109@sandeen.net \
--to=sandeen@sandeen.net \
--cc=lists@colorremedies.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.