From: "Robert Mueller" <robm@fastmail.fm>
To: linux-scsi@vger.kernel.org
Cc: Hubert Tonneau <hubert.tonneau@fullpliant.org>,
"\"Eric Moore\"" <Eric.Moore@lsil.com>,
Bron Gondwana <brong@fastmail.fm>
Subject: mpt fusion retry status...
Date: Mon, 14 Aug 2006 11:55:56 +1000 [thread overview]
Message-ID: <078801c6bf44$ccd39ee0$0e00cb0a@robm> (raw)
I'm just trying to find out what the current status of the mpt fusion driver
in linux 2.6 is with regard to error conditions. We recently came across
some errors in our logs that we think are responsible for corruption on one
of our SCSI connected volumes (kernel 2.6.16.19)
Jul 30 19:25:25 lb1 kernel: mptscsih: ioc1: attempting task abort!
(sc=c4f3c500)
Jul 30 19:25:25 lb1 kernel: sd 1:0:5:0:
Jul 30 19:25:25 lb1 kernel: mptscsih: ioc1: task abort: SUCCESS
(sc=c4f3c500)
Jul 30 19:25:25 lb1 kernel: mptscsih: ioc1: attempting task abort!
(sc=d125e980)
Jul 30 19:25:25 lb1 kernel: sd 1:0:5:0:
Jul 30 19:25:26 lb1 kernel: mptscsih: ioc1: task abort: SUCCESS
(sc=d125e980)
Jul 30 19:25:26 lb1 kernel: mptscsih: ioc1: attempting task abort!
(sc=c21b4380)
Jul 30 19:25:26 lb1 kernel: sd 1:0:5:1:
Jul 30 19:25:26 lb1 kernel: mptscsih: ioc1: task abort: SUCCESS
(sc=c21b4380)
Jul 30 19:25:26 lb1 kernel: mptscsih: ioc1: attempting task abort!
(sc=c7581380)
Jul 30 19:25:26 lb1 kernel: sd 1:0:5:0:
Jul 30 19:25:26 lb1 kernel: mptscsih: ioc1: task abort: SUCCESS
(sc=c7581380)
Searching around, I found this post:
http://www.ussg.iu.edu/hypermail/linux/kernel/0510.1/0705.html
Well it seems that things didn't go into a loop, or cause the device to go
offline, but sometime after the above event we found that doing a check on
the filesystem found some corruption. I can't exactly pinpoint the problem
to the above event, but it seems the most likely event in the logs to be
related to this.
Searching around some more, other people reported the problem:
http://blog.linuri.de/?p=86
So I guess what I'm wondering is what state is the driver with regard to
errors and retrying? With the events in the log above, could that have been
what caused corruption on the filesystem somehow?
Rob
reply other threads:[~2006-08-14 1:55 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='078801c6bf44$ccd39ee0$0e00cb0a@robm' \
--to=robm@fastmail.fm \
--cc=Eric.Moore@lsil.com \
--cc=brong@fastmail.fm \
--cc=hubert.tonneau@fullpliant.org \
--cc=linux-scsi@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