From: George Rapp <george.rapp@gmail.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Linux-RAID <linux-raid@vger.kernel.org>,
Matthew Krumwiede <matt.krumwiede@me.com>
Subject: Re: RAID 5 reshape stalled at 77.5% - next steps??
Date: Sat, 28 Jan 2017 18:58:57 -0500 [thread overview]
Message-ID: <CAF-KpgaXQCjdUnsLjcC55kOCrzFgh5rPFuW8HpoUT4YNsbBELw@mail.gmail.com> (raw)
In-Reply-To: <20170129043338.235723a7@natsu>
On Sat, Jan 28, 2017 at 6:33 PM, Roman Mamedov <rm@romanrm.net> wrote:
> On Sat, 28 Jan 2017 18:29:32 -0500
> George Rapp <george.rapp@gmail.com> wrote:
>
>> Attempting to re-add /dev/sdg4 to the array fails on a busy device:
>>
>> # mdadm --manage /dev/md4 --re-add /dev/sdg4
>> mdadm: Cannot open /dev/sdg4: Device or resource busy
>
> You need to remove it first
>
> mdadm --remove /dev/md4 /dev/sdg4
>
> or
>
> mdadm --remove /dev/md4 faulty
>
> But honestly I am not sure if simply removing and re-adding will bring your
> reshape back to its working order at this point.
>
> Also you should figure out why did it fail in the first place. Check
> SMART, check dmesg further back rather than a few lines only. Maybe the disk
> needs a replacement, not just a blind re-add.
Perhaps not surprisingly, the --remove command also hung.
/dev/sdg4 apparently suffered an uncorrectable read error. Entire
dmesg output (2172 lines) is at
https://app.box.com/s/7brp7c53a51zw4ez5to0m12oc5hxeq92 for your
reference.
Since none of the mdadm commands will respond, I'm thinking we need to
reboot the machine at this point to do any more diagnostics.
Thanks for your quick replies!
--
George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com
LinkedIn profile: https://www.linkedin.com/in/georgerapp
Phone: +1 740 936 RAPP (740 936 7277)
prev parent reply other threads:[~2017-01-28 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 23:01 RAID 5 reshape stalled at 77.5% - next steps?? George Rapp
2017-01-28 23:15 ` Roman Mamedov
2017-01-28 23:29 ` George Rapp
2017-01-28 23:33 ` Roman Mamedov
2017-01-28 23:58 ` George Rapp [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=CAF-KpgaXQCjdUnsLjcC55kOCrzFgh5rPFuW8HpoUT4YNsbBELw@mail.gmail.com \
--to=george.rapp@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=matt.krumwiede@me.com \
--cc=rm@romanrm.net \
/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).