From: Forrest Taylor <ftaylor@redhat.com>
To: "David M. Strang" <dstrang@shellpower.net>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid5: Disk failure on sdm, disabling device
Date: Wed, 31 Aug 2005 16:19:51 -0600 [thread overview]
Message-ID: <1125526791.3194.32.camel@x1-6-00-0d-60-fd-e8-4c> (raw)
In-Reply-To: <00c901c5ae73$b80e3ca0$c100a8c0@NCNF5131FTH>
On Wed, 2005-08-31 at 15:34, David M. Strang wrote:
> ----- Original Message -----
> From: Michael Tokarev
> To: David M. Strang
> Cc: Linux RAID
> Sent: Wednesday, August 31, 2005 5:29 PM
> Subject: Re: raid5: Disk failure on sdm, disabling device
>
> Michael Tokarev wrote:
> > David M. Strang wrote:
> > []
> >
> > > Is there something a little deeper to this error message?
> > >
> > > Aug 31 04:48:15 abyss kernel: scsi2 (12:0): rejecting I/O to offline
> > > device
> > > Aug 31 04:48:15 abyss kernel: raid5: Disk failure on sdm, disabling
> > > device.
> >
> > If you reread my message, I hope you will find a bit of clue:
> >
> > echo y > /sys/block/sdm/device/delete
> > (or something like that anyway.)
> >
> > That's needed for exactly this purpose: to remove a device which is
> > marked 'offline' in the kernel somewhere - to be able to re-add it
> > later - either with this script or just doing that magic add-single-device
> > command manually.
>
> I should have listened sooner; I wasn't able to follow the paths in the
> re-add command, so I didn't do the delete.
>
> I did the delete (the above syntax is correct) -- ran the rescan script, it
> added it back - and the device is accessable again.
>
> Thank you Michael & Forrest.
I just noticed that in /sys/block/sda/device/, along with the delete
file, there is a rescan file. I think that this is what I was thinking
of with the 2.6 kernel.
Forrest
next prev parent reply other threads:[~2005-08-31 22:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 19:26 raid5: Disk failure on sdm, disabling device David M. Strang
2005-08-31 19:28 ` Forrest Taylor
2005-08-31 19:38 ` David M. Strang
2005-08-31 19:29 ` Michael Tokarev
2005-08-31 19:41 ` David M. Strang
2005-08-31 20:07 ` Michael Tokarev
2005-08-31 20:28 ` David M. Strang
2005-08-31 20:35 ` Michael Tokarev
2005-08-31 20:39 ` Forrest Taylor
2005-08-31 20:45 ` David M. Strang
2005-08-31 20:53 ` David M. Strang
2005-08-31 20:59 ` Forrest Taylor
2005-08-31 20:53 ` Forrest Taylor
2005-08-31 21:01 ` David M. Strang
2005-08-31 21:02 ` Forrest Taylor
2005-08-31 21:05 ` David M. Strang
2005-08-31 21:29 ` Michael Tokarev
2005-08-31 21:34 ` David M. Strang
2005-08-31 22:19 ` Forrest Taylor [this message]
2005-09-01 7:38 ` David M. Strang
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=1125526791.3194.32.camel@x1-6-00-0d-60-fd-e8-4c \
--to=ftaylor@redhat.com \
--cc=dstrang@shellpower.net \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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