From: NeilBrown <neilb@suse.de>
To: Sandra Escandor <sescandor@evertz.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: clarifying what can be done during resync
Date: Mon, 27 Jun 2011 15:47:29 +1000 [thread overview]
Message-ID: <20110627154729.521e875a@notabene.brown> (raw)
In-Reply-To: <C70A636B101FD44999B82525C3E92AFAD374BD@otis.burlington.evertz.tv>
On Thu, 23 Jun 2011 15:38:06 -0400 "Sandra Escandor" <sescandor@evertz.com>
wrote:
> Hello,
>
> Just wanted to make sure if this was a myth or not: Is it true that when
> an array is in resync status, then mounting it is not at all possible?
>
Pure myth. Where did you hear it?
Best approach is to try .. if it is not at all possible, then it won't work.
But in fact it does :-)
NeilBrown
next prev parent reply other threads:[~2011-06-27 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 19:38 clarifying what can be done during resync Sandra Escandor
2011-06-27 5:47 ` NeilBrown [this message]
2011-06-27 12:35 ` Sandra Escandor
2011-06-27 12:55 ` David Brown
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=20110627154729.521e875a@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sescandor@evertz.com \
/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).