From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: 4k sector drives
Date: Fri, 23 Jul 2010 05:58:32 -0400 [thread overview]
Message-ID: <20100723095832.GA23174@infradead.org> (raw)
In-Reply-To: <201007230809.28111@zmi.at>
On Fri, Jul 23, 2010 at 08:09:27AM +0200, Michael Monnerie wrote:
> On Mittwoch, 21. Juli 2010 Khelben Blackstaff wrote:
> > Nevertheless, you don't have to get them to report 4k to linux. As
> > long as you align the partitions its fine. As i said in the other
> > post, newer fdisk doesn't use "DOS compatibility mode" and uses
> > sectors by default (instead of stupid CHS) with a 1MB alignment, so
> > every partition will be properly aligned. If you don't dual boot
> > Windows, you can also use GPT partitioning scheme. Also, from what i
> > have seen, xfsprogs are quite clever and find most stuff on their
> > own. I usually mkfs with "-s size=4096" just to be sure.
>
> I always do -b size=4096 anyway, so I'm fine here. And I created the
> partitions starting sector 512, so that should be good also.
-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.
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?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-23 9:55 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 [this message]
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
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=20100723095832.GA23174@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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