All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khelben Blackstaff <eye.of.the.8eholder@gmail.com>
To: xfs@oss.sgi.com
Subject: RE: 4k sector drives
Date: Wed, 21 Jul 2010 10:53:45 +0300	[thread overview]
Message-ID: <201007211053.45191.eye.of.the.8eholder@gmail.com> (raw)

> shows a jumper exists for "advanced format", but doesn't tell what it 
> does. I'll try to set or unset it depending on what it is now, and see 
> if there's a difference.

No, don't set the jumper.

Because DOS required the first head to be empty for some reason
and because allmost every geometry uses 63 sectors per track,
the first partition usually starts at sector 63. The jumper tells the
disk firmware to use a mapping so that the sectors fall in a 4096
boundary. (It uses either +1 or -7 offset). So, the OS thinks it writes
to sector 63 while it truly writes to sector 64 (or 56). Every sector
is transparently mapped using this offset.

This jumper exists to be used only with legacy OSes like Windows XP
and makes sense when there is only one primary partition which covers
the whole disk.

So, don't use the jumper in linux but align properly the partitions.
fdisk from util-linux-ng > 0.17 align on 1MB so everything will be fine.
If you use an older version then align the partitions manually.

WD EARS drives with 00Y model revision doesn't report the sector size
properly and only report 512 bytes. (Use hdparm to see it)
Those with 00Z revision report correctly that they have 4096 physical
sector size and 512 logical sector size.

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

             reply	other threads:[~2010-07-21  7:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  7:53 Khelben Blackstaff [this message]
2010-07-21  9:14 ` 4k sector drives Michael Monnerie
2010-07-21 10:33   ` Emmanuel Florac
  -- 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 10:33 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
2010-07-25 15:33             ` Christoph Hellwig
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=201007211053.45191.eye.of.the.8eholder@gmail.com \
    --to=eye.of.the.8eholder@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.