From: Richard Scobie <richard@sauce.co.nz>
To: linux-raid@vger.kernel.org
Subject: Re: No resync
Date: Wed, 13 Jan 2010 07:27:20 +1300 [thread overview]
Message-ID: <4B4CBF08.30700@sauce.co.nz> (raw)
In-Reply-To: <20100112083753.GA9891@cthulhu.home.robinhill.me.uk>
Robin Hill wrote:
> You probably need to start it with missing members then, so it's able to
> run but not to resync.
This is not an option in assemble mode either. It looks as though the
array has to be recreated. I'm not sure why any of these options are not
provided for assemble.
Anyway, in the end I did an "assemble --force" after stopping what was
left (5 drives dropped from a 16 drive RAID6), and it strated but did
not initiate a resync.
Perhaps the behaviour here has changed, because I'm sure when I've done
this in the past, it resyncs straight away.
There were some somewhat strange errors in the log:
Jan 12 17:09:09 sam kernel: end_request: I/O error, dev sdf, sector
1953182527
Jan 12 17:09:09 sam kernel: md: super_written gets error=-5, uptodate=0
Jan 12 17:09:09 sam kernel: raid5: Disk failure on sdf1, disabling device.
Jan 12 17:09:09 sam kernel: raid5: Operation continuing on 15 devices.
Jan 12 17:09:09 sam kernel: end_request: I/O error, dev sdh, sector
1953182527
Jan 12 17:09:09 sam kernel: md: super_written gets error=-5, uptodate=0
Jan 12 17:09:09 sam kernel: raid5: Disk failure on sdh1, disabling device.
Jan 12 17:09:09 sam kernel: raid5: Operation continuing on 14 devices.
Jan 12 17:09:09 sam kernel: end_request: I/O error, dev sdg, sector
1953182527
Jan 12 17:09:09 sam kernel: md: super_written gets error=-5, uptodate=0
Jan 12 17:09:09 sam kernel: raid5: Disk failure on sdg1, disabling device.
Jan 12 17:09:09 sam kernel: raid5: Operation continuing on 13 devices.
Jan 12 17:09:09 sam kernel: end_request: I/O error, dev sdp, sector
1953182527
Jan 12 17:09:09 sam kernel: md: super_written gets error=-5, uptodate=0
Jan 12 17:09:09 sam kernel: raid5: Disk failure on sdp1, disabling device.
Jan 12 17:09:09 sam kernel: raid5: Operation continuing on 12 devices.
Jan 12 17:09:09 sam kernel: end_request: I/O error, dev sdr, sector
1953182527
Jan 12 17:09:09 sam kernel: md: super_written gets error=-5, uptodate=0
Jan 12 17:09:09 sam kernel: raid5: Disk failure on sdr1, disabling device.
Jan 12 17:09:09 sam kernel: raid5: Operation continuing on 11 devices.
The cause is a controller problem, but after the first 2 drives were
disabled, I don't know why there were "raid5: Operation continuing
on..." messages as another 3 drives were offlined. A RAID6 array should
stop when a third device fails.
Regards,
Richard
next prev parent reply other threads:[~2010-01-12 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 4:44 No resync Richard Scobie
2010-01-12 4:52 ` Leslie Rhorer
2010-01-12 4:58 ` Richard Scobie
2010-01-12 8:37 ` Robin Hill
2010-01-12 18:27 ` Richard Scobie [this message]
2010-01-18 3:48 ` Neil 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=4B4CBF08.30700@sauce.co.nz \
--to=richard@sauce.co.nz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.