From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: NAS Remote Side of a Mirror
Date: Tue, 6 Oct 2009 08:36:45 -0700 (PDT) [thread overview]
Message-ID: <177866.95801.qm@web38807.mail.mud.yahoo.com> (raw)
In-Reply-To: <20091006152443.GA3151@cthulhu.home.robinhill.me.uk>
--- On Tue, 10/6/09, Robin Hill <robin@robinhill.me.uk> wrote:
> > 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?
> >
> The network can be brought up from within the initrd, so
> there's no need
> for the array to wait (that's even more trivial if you just
> have /home
> on the array as you suggest below). Alternately, you
> could use
> write-intent bitmaps, in which case the resync should be
> very quick (you
> may want these anyway - depends how reliable the network
> connection and
> NAS is).
Wow, this is good news. I'll do some research.
It's a freaky quantum world, when you don't even need a partition...
Ya have write-intent bitmaps enabled already, thanks.
next prev parent reply other threads:[~2009-10-06 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 15:37 NAS Remote Side of a Mirror adfas asd
2009-10-06 15:24 ` Robin Hill
2009-10-06 15:36 ` adfas asd [this message]
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=177866.95801.qm@web38807.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 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).