From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: NAS Remote Side of a Mirror
Date: Mon, 5 Oct 2009 08:37:37 -0700 (PDT) [thread overview]
Message-ID: <905067.19304.qm@web38806.mail.mud.yahoo.com> (raw)
I'm looking at setting up my RAID mirrored array so that one side of the mirror is in the HTPC and the other is NASsed in the garage, in case of theft or fire.
I am concerned about the boot process though, as the NASsed side will not be available until the network comes up. Will the array be able to be patient for that and include that side once it comes up, and run not degraded?
What if I lose my local side of the mirror? Is failover possible to the NAS side? (Assuming a separate boot disk with everything except /home, which is on the array)
The only other technology I am aware of which can remote drives at distance is fibrechannel, and that's too expensive, so it seems I'm stuck with GB ethernet. Are there in fact any other options?
Is it possible to bring up ethernet early in the boot process with initrd.img?
Has anyone actually done any of this?
next reply other threads:[~2009-10-05 15:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 15:37 adfas asd [this message]
2009-10-06 15:24 ` NAS Remote Side of a Mirror Robin Hill
2009-10-06 15:36 ` adfas asd
2009-10-07 23:49 ` adfas asd
2009-10-08 0:50 ` Chris Green
2009-10-08 11:39 ` adfas asd
2009-10-08 11:53 ` John Robinson
2009-10-08 12:15 ` adfas asd
2009-10-08 13:10 ` John Robinson
2009-10-08 13:39 ` adfas asd
2009-10-08 7:51 ` Robin Hill
2009-10-08 13:12 ` russ
2009-10-08 13:55 ` adfas asd
2009-10-10 7:13 ` Leslie Rhorer
2009-10-10 12:49 ` adfas asd
2009-10-10 14:21 ` Drew
2009-10-10 14:27 ` adfas asd
2009-10-10 14:28 ` Thomas Fjellstrom
2009-10-10 14:30 ` adfas asd
2009-10-11 7:00 ` Leslie Rhorer
-- strict thread matches above, loose matches on Subject: below --
2009-10-08 13:06 adfas asd
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=905067.19304.qm@web38806.mail.mud.yahoo.com \
--to=chimera_god@yahoo.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 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.