All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Klingner <klingner@stanford.edu>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid1 with rotating offsite disks for backup
Date: Mon, 7 Feb 2011 17:32:48 -0800	[thread overview]
Message-ID: <47409A64-9CF1-4E12-9DAD-F7079298B1FE@stanford.edu> (raw)
In-Reply-To: <20110208121923.5908630d@notabene.brown>

>>>> Also, if you want two rotating backups I would create two stacked raid1s.
>>>> 
>>>> mdadm -C /dev/md0 -l1 -n2 -b internal  /dev/main-device /dev/first-backup
>>>> mdadm -C /dev/md1 -l1 -n2 -b internal /dev/md0 /dev/second-backup
>>>> mkfs -j /dev/md1



On Feb 7, 2011, at 5:19 PM, NeilBrown wrote:
> I'm surprised that you found the correct advise, and chose not to follow
> it .....

Thanks again for your advice.  I didn't search the list until after completing my initial setup; my mistake and my lesson learned: research first.

> The array you will end up installing on is (slightly) smaller than than the
> array you have created.  So no: you cannot re-arrange things - you have to
> start again.
> 
> 
> (well, to be honest, it is possible that you could resize whatever is on the
> array and then build the secondary array and make it work.  But that path is
> error-prone and this margin is not large enough to properly describe the
> process).

Reckless fool that I am, I'm going to try it anyway.  Here's my rough plan:

1. Degrade the 3-disk raid1 array by removing two disks, leaving only one, and leaving the array running.
2. Set up the first 2-disk array (md0 in your description) de novo on the two freed disks
3. Move my data from the original raid1 array (with only 1 of three disks present) to the new 2-disk md0 via lvm mirroring
4. Free the third disk by finally taking down the original raid1 array
5. create the second 2-device array (md1) using md0 and the freed third disk.  Somehow ensure that the md0 component has primacy for syncing.

Jeff


  reply	other threads:[~2011-02-08  1:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 23:53 raid1 with rotating offsite disks for backup Jeff Klingner
2011-02-08  0:17 ` NeilBrown
2011-02-08  1:03   ` Jeff Klingner
2011-02-08  1:19     ` NeilBrown
2011-02-08  1:32       ` Jeff Klingner [this message]
2011-02-08  2:02         ` NeilBrown
2011-02-08  4:53   ` Leslie Rhorer
2011-02-08  5:37     ` Roberto Spadim
2011-02-08  6:07       ` NeilBrown
2011-02-08  6:12         ` Roberto Spadim
2011-02-08  3:04 ` Martin Cracauer
2011-02-08  3:40   ` Roberto Spadim
2011-02-09 19:37 ` hansbkk
2011-02-09 19:53   ` Roberto Spadim
2011-02-10  8:43     ` John Robinson

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=47409A64-9CF1-4E12-9DAD-F7079298B1FE@stanford.edu \
    --to=klingner@stanford.edu \
    --cc=linux-raid@vger.kernel.org \
    --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.