From: Matt Darcy <kernel-lists@projecthugo.co.uk>
To: linux-raid@vger.kernel.org
Subject: RAID 5 - Botched Output information
Date: Tue, 20 Dec 2005 10:42:00 +0000 [thread overview]
Message-ID: <43A7DFF8.80203@projecthugo.co.uk> (raw)
Hello all,
I'm experimenting with the experimental "sata_mv" driver in the
2.6.15-rc5-mm kernel.
I've found it "works" but its rather flakey and fails a lot (I'll be
posting seperate information on this in another post)
I've just created a raid 5 array as a test made up of 5 x 250 GB sata disks.
It seems to complete after a life time (hey - its a lot of disk - no rush)
However dmesg shows the following ouptut (just included the raid 5
devices output)
md: md6: sync done.
RAID5 conf printout:
--- rd:5 wd:5 fd:0
disk 0, o:1, dev:sdc1
disk 1, o:1, dev:sdd1
disk 2, o:1, dev:sde1
disk 3, o:1, dev:sdf1
disk 4, o:1, dev:sdg1
ata10: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata10: status=0xd0 { Busy }
ata9: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata9: status=0xd0 { Busy }
blk: request botched
ata8: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata8: status=0xd0 { Busy }
blk: request botched
ata6: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata6: status=0xd0 { Busy }
blk: request botched
ata4: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata4: status=0xd0 { Busy }
blk: request botched
I'm interested in the statement blk: request botched
Google turns up many interesting theories about this statments which
seems to be caused by meny theoretical solutions (I think the people
responding on the threads found on google are making random guesses to
be honest)
I thought I'd ask here to get a better understanding of the "blk:
request botched" statement.
Thanks for the input.
Matt
reply other threads:[~2005-12-20 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43A7DFF8.80203@projecthugo.co.uk \
--to=kernel-lists@projecthugo.co.uk \
--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).