From: "Desai, Kashyap" <Kashyap.Desai@lsi.com>
To: Lukas Kolbe <lkolbe@TechFak.Uni-Bielefeld.DE>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: RE: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec
Date: Thu, 19 Nov 2009 10:43:38 +0530 [thread overview]
Message-ID: <0D1E8821739E724A86F4D16902CE275C1C93C74BD4@inbmail01.lsi.com> (raw)
In-Reply-To: <20091118133909.GD16440@TechFak.Uni-Bielefeld.DE>
> -----Original Message-----
> From: Lukas Kolbe [mailto:lkolbe@TechFak.Uni-Bielefeld.DE]
> Sent: Wednesday, November 18, 2009 7:09 PM
> To: Desai, Kashyap
> Cc: linux-scsi@vger.kernel.org
> Subject: Re: Bug 14579 - Devices disappear... and Bug 14577 - Data
> corruption with Adaptec
>
> Desai, Kashyap wrote:
>
> >> >Subject line is related to *Adaptec* and there are some places LSI
> >> >related issue is pointed out. Little confusing to me. Is it possible
> to
> >> >rewrite what is an issue related to LSI card?
> >>
> >> Sorry for that one. This system has an Adaptec Controller for its
> >> Storage array and an LSI controller for the tape library. Bug 14577 is
> >> about a possible data corruption on 2.6.32-rc6 that seems to be either
> a
> >> hardware error (currently trying to find that out) or a regression in
> >> 2.6.32-rc6, as 2.6.30 is very happy with its storage.
> >OK. In data corruption condition only LSI driver and controller are
> >involved? I mean can I nullify Adaptec controller's roll in your test?
>
> No, it is the other way round. We have 24 1TB Seagate harddisks
> connected in a RAID 60 to the adaptec controller, and a Tandberg T80
> with two IBM Ultrium-HH4 tape drives connected to the LSI controller.
>
> The system is installed on an LVM volume within the RAID 60.
> The data corruption occurs when we try to boot 2.6.32-rc6, we get write
> errors and the boot process stops somewhere. So, it seems the data
> corruption is related _only_ with the Adaptec Controller, the RAID array
> or the harddisks.
>
> >> Finally, the real problem here is Bug 14579 that is about the systems
> >> problems when using the tape library.
> >>
> >> >From dmesg log I can figure out 3.04.07 is mpt fusion driver version.
> >> >Please update LSI driver using latest upstream driver version 3.04.13.
> >> And see what a result is.
> >>
> >> Thanks for the pointer. Linus' current tree contains 3.04.12 - where
> can
> >> I find 3.04.13?
> >
> >It is there in 2.6.32-rc5. Not sure in which exact rc version it is
> >included, but I have 2.6.32-rc5 tree in my setup and for that kernel
> >mptfusion version is 3.104.13
>
> Okay, I grep'ed for 3.04 in the source and only got one reference to the
> older version number. But there lies the problem: Unless we can fix the
> Adaptec-Bug first (or confirm it is a hardware issue), we can't boot
> 2.6.32-rc on that machine to test the new LSI driver version. Is it
> easily possible to backport/include the mptfusion in 2.6.30?
OK. So I get it now. You are working to solve major issue which is related to your RAID 60 + Adaptec controller. If you want to upgrade LSI driver, we can always go for latest driver. I can provide you latest driver source tar ball. Back porting to 2.6.30 is fine.
>
> Thanks for the help and kind regards,
> --
> Lukas Kolbe
next prev parent reply other threads:[~2009-11-19 5:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 16:02 Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec Lukas Kolbe
2009-11-12 22:58 ` Sascha Frey
2009-11-13 11:59 ` Desai, Kashyap
2009-11-17 14:22 ` Lukas Kolbe
2009-11-18 4:54 ` Desai, Kashyap
2009-11-18 13:39 ` Lukas Kolbe
2009-11-19 5:13 ` Desai, Kashyap [this message]
2009-11-19 10:17 ` Bug 14579 (was: RE: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec) Lukas Kolbe
2009-11-19 10:30 ` Desai, Kashyap
2009-11-19 10:48 ` Lukas Kolbe
2009-11-19 10:58 ` Desai, Kashyap
2009-11-19 11:11 ` Bug 14579 Lukas Kolbe
2010-02-03 13:36 ` Bug 14579 (was: RE: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec) Lukas Kolbe
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=0D1E8821739E724A86F4D16902CE275C1C93C74BD4@inbmail01.lsi.com \
--to=kashyap.desai@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lkolbe@TechFak.Uni-Bielefeld.DE \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.