linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: EJ Vincent <ej@ejane.org>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Manually failing a disk during a md raid6 reshape
Date: Tue, 04 Dec 2012 13:44:56 -0500	[thread overview]
Message-ID: <50BE44A8.1040502@ejane.org> (raw)

Greetings,

I currently have a md raid6 reshape (growth, adding a disk) under-way.  
Dmesg is beginning to fill up with:

[23661.913556] ata15.00: status: { DRDY }
[23661.914443] ata15.00: failed command: WRITE FPDMA QUEUED
[23661.915326] ata15.00: cmd 61/80:f0:00:34:e9/00:00:45:00:00/40 tag 30 
ncq 65536 out
[23661.915329]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 
0x4 (timeout)
[23661.917110] ata15.00: status: { DRDY }
[23661.917977] ata15: hard resetting link
[23664.116087] ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[23664.118667] ata15.00: configured for UDMA/100
[23664.118685] ata15.00: device reported invalid CHS sector 0

What's the best way to identify ata15.00 and is it permissible to 
manually fail this device, without damaging and/or interrupting the 
reshape?

I'm also perfectly OK with waiting for it to complete on it's own, 
although the speed of the reshape operation has diminished, by my 
estimate, about 25% since beginning.

Also, any conjecture on what might lead to the above error(s)?

Thank you very much.

Best,
-EJ

             reply	other threads:[~2012-12-04 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 18:44 EJ Vincent [this message]
2012-12-05 13:24 ` Manually failing a disk during a md raid6 reshape Mikael Abrahamsson
2012-12-06  3:47 ` Jack Wang

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=50BE44A8.1040502@ejane.org \
    --to=ej@ejane.org \
    --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).