From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 wont restart after disk failure, then corrupts
Date: Wed, 1 Mar 2006 12:37:34 +0100 [thread overview]
Message-ID: <20060301113734.GA32059@percy.comedia.it> (raw)
In-Reply-To: <20060228220811.GA32469@cjx.com>
On Tue, Feb 28, 2006 at 10:08:11PM +0000, Chris Allen wrote:
>
>Yesterday morning we had an io error on /dev/sdd1:
>
>Feb 27 10:08:57 snap25 kernel: SCSI error : <0 0 3 0> return code = 0x10000
>Feb 27 10:08:57 snap25 kernel: end_request: I/O error, dev sdd, sector 50504271
>Feb 27 10:08:57 snap25 kernel: raid5: Disk failure on sdd1, disabling device. Operation continuing on 7 devices
>
>So, I shutdown the system and replaced drive sdd with a new one.
>When I powered up again, all was not well. The array wouldn't start:
>
>Feb 27 13:36:02 snap25 kernel: md: md0: raid array is not clean -- starting background reconstruction
....
>Feb 27 13:36:02 snap25 kernel: raid5: cannot start dirty degraded array for md0
something happened whan you shut down the system and the superblock on
the drives was not updated
>I tried assembling the array with --force, but this would produce exactly the
>same results as above - the array would refuse to start.
>
>QUESTION: What should I have done here? Each time I have tried this in the past, I
recreate the array with a missing drive in place of sdd.
mount your fs readonly (as ext2 in case it was ext3) and verify that all
data is readable.
>have had no problems restarting the array and adding the new disk. What had gone
>wrong, and why wouldn't the array start?
something happened whan you shut down the system and the superblock on
the drives was not updated
>Then things went from bad to worse.
>
>
>===========================================
>PROBLEM 2 - DATA CORRUPTION
>===========================================
>
>
>1. Any idea what had happened here? Why didn't it notice that sdd1 was stale?
something happened whan you shut down the system and the superblock on
the drives was not updated
>
>2. If I had let it complete its resync would it have sorted out the corruption?
no
>Or would it have made things worse?
possibly yes
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
prev parent reply other threads:[~2006-03-01 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 22:08 raid5 wont restart after disk failure, then corrupts Chris Allen
2006-03-01 11:37 ` Luca Berra [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=20060301113734.GA32059@percy.comedia.it \
--to=bluca@comedia.it \
--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).