From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 reshape problems
Date: Wed, 25 Mar 2009 21:11:53 +0100 [thread overview]
Message-ID: <49CA9009.304@xunil.at> (raw)
In-Reply-To: <49CA787C.2090100@xunil.at>
Just as an addition while I am waiting desparately ...
here the section of dmesg:
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: Device offlined - not ready after error recovery
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 42380636
raid5: Disk failure on sdf4, disabling device. Operation continuing on 5
devices
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 42379612
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929100
raid5:md2: read error not correctable (sector 5000560 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929092
raid5:md2: read error not correctable (sector 5000552 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929084
raid5:md2: read error not correctable (sector 5000544 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929108
raid5:md2: read error not correctable (sector 5000568 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22928988
raid5:md2: read error not correctable (sector 5000448 on sdf4).
raid5:md2: read error not correctable (sector 5000456 on sdf4).
raid5:md2: read error not correctable (sector 5000464 on sdf4).
raid5:md2: read error not correctable (sector 5000472 on sdf4).
raid5:md2: read error not correctable (sector 5000480 on sdf4).
raid5:md2: read error not correctable (sector 5000488 on sdf4).
raid5:md2: read error not correctable (sector 5000496 on sdf4).
raid5:md2: read error not correctable (sector 5000504 on sdf4).
raid5:md2: read error not correctable (sector 5000512 on sdf4).
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdf, sector 22929060
raid5:md2: read error not correctable (sector 5000520 on sdf4).
raid5:md2: read error not correctable (sector 5000528 on sdf4).
raid5:md2: read error not correctable (sector 5000536 on sdf4).
end_request: I/O error, dev sdf, sector 1953519836
md: super_written gets error=-5, uptodate=0
sd 0:0:5:0: [sdf] Result: hostbyte=0x01 driverbyte=0x00
md: md2: reshape done.
next prev parent reply other threads:[~2009-03-25 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 18:31 RAID5 reshape problems Stefan G. Weichinger
2009-03-25 20:11 ` Stefan G. Weichinger [this message]
2009-03-25 22:13 ` Neil Brown
2009-03-25 22:43 ` Stefan G. Weichinger
2009-03-26 6:58 ` Stefan G. Weichinger
2009-03-26 10:20 ` Stefan G. Weichinger
2009-03-27 18:11 ` RAID5 reshape problems : SOLVED Stefan G. Weichinger
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=49CA9009.304@xunil.at \
--to=lists@xunil.at \
--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).