linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wil Reichert <wil.reichert@gmail.com>
To: Peter Kieser <peter@kieser.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mixing 512-byte sector, and 4096-byte sector drives
Date: Mon, 22 Mar 2010 17:11:44 -0700	[thread overview]
Message-ID: <7a329d911003221711r153693f6jdaec0b4f4b3d634@mail.gmail.com> (raw)
In-Reply-To: <4BA7FFA9.7040303@kieser.ca>

On Mon, Mar 22, 2010 at 4:39 PM, Peter Kieser <peter@kieser.ca> wrote:
> Hello,
>
> I have a 6-drive RAID6 of WD15EADS (512-byte sector) drives. One of the
> drives is failing, and I have been forced to buy a WD15EARS (4096-byte
> sector) drive to replace the failing drive, and it has the new "advanced
> format" technology.
>
> Do I need to set the "XP" jumper on pins 7-8 to play nicely with the other
> 512-byte sector drives in my array, or will mdraid be okay with the
> 4096-byte sector drive? Will there be a performance penalty adding the drive
> to my array?

Did you create your RAID on the device or on a partition?  If its on
the entire device then you should be fine, tho this might depend on
which metadata format you are using & where its located on the disc
(not sure how the metadata effects data alignment).  If you used a
standard partitioning tool its likely your partitions start on sector
63.  This can be confirmed via an fdisk -l on your other drives.  If
that's the case then you'll probably want to use the offest jumper.
How the drive will behave with the others I have no idea.  If after
you add the drive and your write speeds drop dramatically then
something is misaligned.

Wil

  reply	other threads:[~2010-03-23  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 23:39 Mixing 512-byte sector, and 4096-byte sector drives Peter Kieser
2010-03-23  0:11 ` Wil Reichert [this message]
2010-03-23 18:53   ` Peter Kieser

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=7a329d911003221711r153693f6jdaec0b4f4b3d634@mail.gmail.com \
    --to=wil.reichert@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=peter@kieser.ca \
    /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;
as well as URLs for NNTP newsgroup(s).