public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@sandeen.net>
Subject: Re: 4k sector drives
Date: Sun, 25 Jul 2010 00:35:21 +0200	[thread overview]
Message-ID: <201007250035.25946@zmi.at> (raw)
In-Reply-To: <4C4B55F7.2090501@sandeen.net>


[-- Attachment #1.1: Type: Text/Plain, Size: 1400 bytes --]

On Samstag, 24. Juli 2010 Eric Sandeen wrote:
> > If it really is one using -s size=4096 is the right thing to do.
> 
> Haven't read the whole thread so maybe this is redundant, but make
> sure all partitions (if any) are 4k aligned as well (unless it has
> the secret-handshake sector 63 offset...)
 
Thank you Christoph for clarification, also thanks to Eric - I've been 
aligning all partitions to a multiple of 512 sectors since a long time, 
which fits all stripe set sizes up to 256k. Too bad that even Linux 
fdisk and parted still don't do something like that, today I setup a 
Novell SLES 11 with XEN VM, and everywhere parted would align the first 
partition (when using GPT) to sector 34.. what a number.. Good that 4K 
sector drives arrive now, so the tools will hopefully change for a 
better default.

BTW: AFAIK SSD drives have a (sometimes very large) internal alignment 
of bytes which should be used as a "stripe size" to meet the optimal I/O 
size. Is there a way to find out how big that is yet?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

  reply	other threads:[~2010-07-24 22:32 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
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 [this message]
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=201007250035.25946@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --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