From: Roman Mamedov <rm@romanrm.net>
To: Dan Knight <dknight1989@woh.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [Question] how to proceed after bad raid5 reshape
Date: Wed, 23 Oct 2013 04:16:40 +0600 [thread overview]
Message-ID: <20131023041640.0e8ae338@natsu> (raw)
In-Reply-To: <5266F5F8.4040503@woh.rr.com>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Tue, 22 Oct 2013 18:02:32 -0400
Dan Knight <dknight1989@woh.rr.com> wrote:
> Checking mdadm -Evvvvs shows that maybe 2 drives went bad during the
> reshape?
And maybe, just maybe, `dmesg` would have something about this, if this indeed
happened. But of course asking people on the internet to play with you an
exciting game of guesswork is much more exciting than looking at the actual
log which would simply and boringly TELL you what exactly happened...
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-10-22 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 22:02 [Question] how to proceed after bad raid5 reshape Dan Knight
2013-10-22 22:16 ` Roman Mamedov [this message]
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=20131023041640.0e8ae338@natsu \
--to=rm@romanrm.net \
--cc=dknight1989@woh.rr.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).