All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: 4k sector drives
Date: Fri, 23 Jul 2010 08:10:35 -0500	[thread overview]
Message-ID: <4C4994CB.2050200@hardwarefreak.com> (raw)
In-Reply-To: <201007231259.11714@zmi.at>

Michael Monnerie put forth on 7/23/2010 5:59 AM:
> On Freitag, 23. Juli 2010 Christoph Hellwig wrote:
>> -b size=4096 is the default anyway, for 4k sector drivers you also
>>  want -s size=4096, which you do not want for 512 byte sector disks.
> 
> Thanks for clarification. Should I use "-s size=4096" despite the drive 
> saying 512b sectors? It's a "hidden" 4K sector drive, so maybe declaring 
> it extra for XFS helps performance? Or does it not matter at all?
>  
>> What values do the files
>>
>>         /sys/block/<device>/queue/logical_block_size
>>         /sys/block/<device>/queue/physical_block_size
>>         /sys/block/<device>/alignment_offset
>>
>> say about your disk?
> 
> 512, 512, 0 for a Western Digital D20EARS-00MVWB0 (2TB) which has 4K 
> sectors but obviously hides it.

The WD20EARS-00MVWB0 is definitely a 4k sector drive:
http://products.wdc.com/Library/Flyer/ENG/2178-771123.pdf

If you're currently seeing somewhere between 60-120MB/s per drive with hdparm
or dd then you don't need to further tweak anything.  If alignment is off,
from all I've read, performance will be abysmal, down in the sub 30MB/s range.

-- 
Stan

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

  parent reply	other threads:[~2010-07-23 13:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 10:33 4k sector drives Khelben Blackstaff
2010-07-21 12:21 ` Michael Monnerie
2010-07-23  6:09 ` Michael Monnerie
2010-07-23  9:58   ` Christoph Hellwig
2010-07-23 10:42     ` Stan Hoeppner
2010-07-23 10:47       ` Christoph Hellwig
2010-07-23 12:41         ` Stan Hoeppner
2010-07-23 10:59     ` Michael Monnerie
2010-07-23 12:56       ` Emmanuel Florac
2010-07-23 13:10       ` Stan Hoeppner [this message]
2010-07-23 13:38         ` Matthias Schniedermeyer
2010-07-23 13:50           ` Emmanuel Florac
2010-07-23 14:13             ` Matthias Schniedermeyer
2010-07-24  8:47       ` Christoph Hellwig
2010-07-24 21:07         ` Eric Sandeen
2010-07-24 22:35           ` Michael Monnerie
2010-07-25 15:33             ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2010-07-23 15:02 Khelben Blackstaff
2010-07-23 15:28 ` Emmanuel Florac
2010-07-23  9:19 Khelben Blackstaff
2010-07-21  7:53 Khelben Blackstaff
2010-07-21  9:14 ` Michael Monnerie
2010-07-21 10:33   ` Emmanuel Florac
2010-07-20 18:58 Michael Monnerie
2010-07-20 20:30 ` Stan Hoeppner
2010-07-20 20:39 ` Emmanuel Florac
2010-07-20 21:34   ` Michael Monnerie

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=4C4994CB.2050200@hardwarefreak.com \
    --to=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 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.