From: Roberto Spadim <roberto@spadim.com.br>
To: Henrik Olsson <henrik@fixme.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mixing 512 bytes and 4K sector harddrives in a raid1?
Date: Mon, 7 Feb 2011 13:07:39 -0200 [thread overview]
Message-ID: <AANLkTimpk+N6GuQXBRYU7teKiL_Chp8gn+uRLt_HoT-p@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=43ujbivEtgq1fyn0hnRRXvJJKmojf7LZhtid9@mail.gmail.com>
speed problem =) (i tested eeheheh)
i was talking about it in this list
i don´t know yet what the internal raid1 sector size (i think it´s the
chuck size defined on mdadm --create, but i´m not sure)
if you use 4k ssd you can see read/write when making <4kb read on ssd,
if it's a hd no problem, ssd will degrade max ssd speed with wrong
sector size (read/write not aligned)
i'm waiting the chunck size answer if you want wait the list to answer...
2011/2/7 Henrik Olsson <henrik@fixme.se>:
> Hi,
>
> One of the drives in my raid1 recently crashed and it looks like all
> the replacement disks (2TB) i can find use 4K sectors, but the old
> ones were 512 bytes.
> Are there any issues with having a raid1 array with different sector
> sizes for the drives?
>
> Regards,
> Henrik
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-07 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:41 Mixing 512 bytes and 4K sector harddrives in a raid1? Henrik Olsson
2011-02-07 13:56 ` David Brown
2011-02-07 14:08 ` Henrik Olsson
2011-02-07 15:07 ` Roberto Spadim [this message]
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=AANLkTimpk+N6GuQXBRYU7teKiL_Chp8gn+uRLt_HoT-p@mail.gmail.com \
--to=roberto@spadim.com.br \
--cc=henrik@fixme.se \
--cc=linux-raid@vger.kernel.org \
/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).