linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david@westcontrol.com>
To: linux-raid@vger.kernel.org
Subject: Re: raid1 mirror optimizations
Date: Wed, 26 Jan 2011 10:49:50 +0100	[thread overview]
Message-ID: <ihoqek$nu4$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTimUbWcHi8w6UzxKjkavpOihV7V5Nm58mV7HA0AE@mail.gmail.com>

On 25/01/2011 19:56, Roberto Spadim wrote:
> hi guys... i have a damaged disk...
> i´m using raid1
> the computer crashed with the floor :P hihiih sorry, but the disks are
> damaged at the same position
> check: http://www.spadim.com.br/hd%20agra.zip
> the problem: since raid1 (mirror) is done with real mirror, the disk
> position are the same...
> if i was using a mirror but on disk 1 i write from beggining to end,
> and disk 2 from end to beggining , i don´t crash the disk at the same
> position, for disk 1 i crash it some bytes, for disk 2 i crash some
> others bytes, since beggining is a small cilinder and end a bigger, i
> could loose less information than mirror
> could we implement a 'inverted' mirror? just for hard disks (for ssd
> it´s a small loss of cpu/memory)
> thanks
>

If you are worried about the disks being in the same position, then I 
assume you mean the heads were in the same position when they crashed 
into the disk.  If that's the case, then it doesn't really matter too 
much if the same bytes on the disk were hit - your disks are trashed 
anyway, and you'll need expensive professional recovery services to deal 
with it.

If you are not talking about head crashes, and merely about corruption 
because the disks were being written to in the same place on both disks, 
then the layout on the disk will make little difference - the same data 
will be written to the same logical place at roughly the same time.  It 
doesn't matter where this data is located physically on the disk, since 
it is the data that matters.  The same thing actually applies to head 
crashes too.

If you really want an "inverted" mirror, there is an easy way to get 
much of the same effect.  Instead of setting up raid1, use raid10 with 
"far 2" positioning.  The effect is roughly like this:

disk1 (stripe 1) (mirror of stripe 2)
disk2 (stripe 2) (mirror of stripe 1)

So the two copies of the data are in different physical positions on 
each disk.  It's not a full reversal, but you can think of disk 2 as 
being split in two and its two halves swapped.


--
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

  parent reply	other threads:[~2011-01-26  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 18:56 raid1 mirror optimizations Roberto Spadim
2011-01-25 20:19 ` Oliver Brakmann
2011-01-26 15:39   ` Roberto Spadim
2011-01-26 16:37     ` Oliver Brakmann
2011-01-26 21:08       ` David Brown
2011-01-26  9:49 ` David Brown [this message]
2011-01-26 14:18   ` Roberto Spadim

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='ihoqek$nu4$1@dough.gmane.org' \
    --to=david@westcontrol.com \
    --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).