From: NeilBrown <neilb@suse.de>
To: Dietrich Heise <dh@dhde.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 faild while in degraded mode, need help
Date: Tue, 10 Jul 2012 09:02:14 +1000 [thread overview]
Message-ID: <20120710090214.286059f2@notabene.brown> (raw)
In-Reply-To: <CACMY3vDNoZN4tt4TRoE=49q9hkrFZ+7NRKgHHQXKe1_=wi8byw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3287 bytes --]
On Mon, 9 Jul 2012 13:02:04 +0200 Dietrich Heise <dh@dhde.de> wrote:
> Hello,
>
> thanks for the hint.
>
> I do a backup with dd before that, I hope I can get back the data of the raid.
>
> The following is in the syslog:
>
> Jul 8 19:21:15 p3 kernel: Buffer I/O error on device dm-1, logical
> block 365625856
> Jul 8 19:21:15 p3 kernel: Buffer I/O error on device dm-1, logical
> block 365625856
> Jul 8 19:21:15 p3 kernel: lost page write due to I/O error on dm-1
> Jul 8 19:21:15 p3 kernel: lost page write due to I/O error on dm-1
> Jul 8 19:21:15 p3 kernel: JBD: I/O error detected when updating
> journal superblock for dm-1.
> Jul 8 19:21:15 p3 kernel: JBD: I/O error detected when updating
> journal superblock for dm-1.
> Jul 8 19:21:15 p3 kernel: RAID conf printout:
> Jul 8 19:21:15 p3 kernel: RAID conf printout:
> Jul 8 19:21:15 p3 kernel: --- level:5 rd:4 wd:2
> Jul 8 19:21:15 p3 kernel: --- level:5 rd:4 wd:2
> Jul 8 19:21:15 p3 kernel: disk 0, o:1, dev:sdf1
> Jul 8 19:21:15 p3 kernel: disk 0, o:1, dev:sdf1
> Jul 8 19:21:15 p3 kernel: disk 1, o:1, dev:sde1
> Jul 8 19:21:15 p3 kernel: disk 1, o:1, dev:sde1
> Jul 8 19:21:15 p3 kernel: disk 2, o:1, dev:sdc1
> Jul 8 19:21:15 p3 kernel: disk 2, o:1, dev:sdc1
> Jul 8 19:21:15 p3 kernel: disk 3, o:0, dev:sdd1
> Jul 8 19:21:15 p3 kernel: disk 3, o:0, dev:sdd1
> Jul 8 19:21:15 p3 kernel: RAID conf printout:
> Jul 8 19:21:15 p3 kernel: RAID conf printout:
> Jul 8 19:21:15 p3 kernel: --- level:5 rd:4 wd:2
> Jul 8 19:21:15 p3 kernel: --- level:5 rd:4 wd:2
> Jul 8 19:21:15 p3 kernel: disk 0, o:1, dev:sdf1
> Jul 8 19:21:15 p3 kernel: disk 0, o:1, dev:sdf1
> Jul 8 19:21:15 p3 kernel: disk 1, o:1, dev:sde1
> Jul 8 19:21:15 p3 kernel: disk 1, o:1, dev:sde1
> Jul 8 19:21:15 p3 kernel: disk 2, o:1, dev:sdc1
> Jul 8 19:21:15 p3 kernel: disk 2, o:1, dev:sdc1
> Jul 8 19:21:15 p3 kernel: md: recovery of RAID array md0
> Jul 8 19:21:15 p3 kernel: md: recovery of RAID array md0
> Jul 8 19:21:15 p3 kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
> Jul 8 19:21:15 p3 kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
> Jul 8 19:21:15 p3 kernel: md: using maximum available idle IO
> bandwidth (but not more than 200000 KB/sec) for recovery.
> Jul 8 19:21:15 p3 kernel: md: using maximum available idle IO
> bandwidth (but not more than 200000 KB/sec) for recovery.
> Jul 8 19:21:15 p3 kernel: md: using 128k window, over a total of 1465126400k.
> Jul 8 19:21:15 p3 kernel: md: using 128k window, over a total of 1465126400k.
> Jul 8 19:21:15 p3 kernel: md: resuming recovery of md0 from checkpoint.
> Jul 8 19:21:15 p3 kernel: md: resuming recovery of md0 from checkpoint.
>
> I think the right order is sdf1 sde1 sdc1 sdd1, I am right?
Yes, that looks right.
>
> So I have to do:
>
> mdadm -C /dev/md1 -l5 -n4 -e 1.2 -c 512 /dev/sdf1 /dev/sde1 missing /dev/sdd1
>
> The question is: sould I also add --assume-clean
--assume-clean makes no difference to a degraded raid5 so it doesn't really
matter.
However I always suggest using --assume-clean when re-creating an array so
on principle I would say "yes - you should add --assume-clean".
NeilBrown
>
> Thanks!
> Dietrich
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-09 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 19:05 RAID5 faild while in degraded mode, need help Dietrich Heise
2012-07-09 0:12 ` NeilBrown
2012-07-09 11:02 ` Dietrich Heise
2012-07-09 23:02 ` NeilBrown [this message]
2012-07-11 18:50 ` Dietrich Heise
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=20120710090214.286059f2@notabene.brown \
--to=neilb@suse.de \
--cc=dh@dhde.de \
--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).