All of lore.kernel.org
 help / color / mirror / Atom feed
From: SandeepKsinha <sandeepksinha@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: lrhorer@satx.rr.com, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Requesting replace mode for changing a disk
Date: Wed, 13 May 2009 10:07:00 +0530	[thread overview]
Message-ID: <37d33d830905122137l18f13c2aoec8e1cf67fdba2c0@mail.gmail.com> (raw)
In-Reply-To: <18954.19719.172893.761454@notabene.brown>

Hi,

On Wed, May 13, 2009 at 10:01 AM, Neil Brown <neilb@suse.de> wrote:
> On Tuesday May 12, lrhorer@satx.rr.com wrote:
>>
>> But doesn't creating the array with the drive wipe the contents?  If so, it
>> doesn't seem to me this provides much redundancy.
>
> No.  Creating an array does not wipe the contents.
> It might cause a resync which will copy contents from one drive to the
> other and I don't promise which one.
> However if you:
>
Now, my question is that what if I create a RAID1 with 100 disks on each side.
Do you mean to say that there will be unnecessary resync happening
there as well, that too for unallocated/written data.

If thats the case, we surely need to handle these two situations
differently (1) which neil mentioned (2) the one I mentioned above.

Remember I referring to the case of creation.

>   mdadm -C /dev/md0 --level 1 -n 2 /dev/foo missing
>   mdadm /dev/md0 --add /dev/bar
>
> then the contents on /dev/foo will not be changed (except for a few K
> at the end for the metadata) and then all of foo will be copied to
> bar.
>

Will the create happen at the first place?
> NeilBrown
> --
> 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
>



-- 
Regards,
Sandeep.





 	
“To learn is to change. Education is a process that changes the learner.”
--
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

  reply	other threads:[~2009-05-13  4:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 22:15 Requesting replace mode for changing a disk Goswin von Brederlow
2009-05-09 11:41 ` John Robinson
2009-05-09 23:07 ` Bill Davidsen
2009-05-10  1:22   ` Goswin von Brederlow
2009-05-10  2:20   ` Guy Watkins
2009-05-10  7:02     ` Goswin von Brederlow
2009-05-10 14:33     ` Bill Davidsen
2009-05-10 15:55       ` Guy Watkins
2009-05-13  1:21   ` Leslie Rhorer
2009-05-13  3:27     ` Goswin von Brederlow
2009-05-13  4:36       ` Neil Brown
2009-05-13  7:37         ` Goswin von Brederlow
2009-05-13 11:02           ` Neil Brown
2009-05-14 10:44         ` David Greaves
2009-05-14 12:00           ` Neil Brown
2009-05-13  4:31     ` Neil Brown
2009-05-13  4:37       ` SandeepKsinha [this message]
2009-05-13  4:54         ` Neil Brown
2009-05-13  5:07           ` SandeepKsinha
2009-05-13  5:21             ` NeilBrown
2009-05-13  5:31               ` SandeepKsinha
2009-05-13 10:51                 ` Neil Brown
2009-05-13  7:28       ` Goswin von Brederlow
2009-05-13  4:08 Sandeep K Sinha

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=37d33d830905122137l18f13c2aoec8e1cf67fdba2c0@mail.gmail.com \
    --to=sandeepksinha@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    --cc=neilb@suse.de \
    /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.