All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Kolbe <lkolbe@TechFak.Uni-Bielefeld.DE>
To: "Desai, Kashyap" <Kashyap.Desai@lsi.com>
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: Tue, 17 Nov 2009 15:22:42 +0100	[thread overview]
Message-ID: <20091117142242.GA15638@TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C1C93C04462@inbmail01.lsi.com>

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. 

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?

>- Kashyap

Kind regards,
Lukas Kolbe


>-----Original Message-----
>From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Sascha Frey
>Sent: Friday, November 13, 2009 4:28 AM
>To: linux-scsi@vger.kernel.org
>Cc: Lukas Kolbe
>Subject: Re: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec
>
>Hi,
>
>Lukas Kolbe wrote:
>>we'd really appreciate any hints and help we can get for the following
>>bugs:
>>http://bugzilla.kernel.org/show_bug.cgi?id=14579
>
>We've done some further testing:
>it's very hard to trigger this bug. Sometimes the machine freezes after
>a few minutes into tape access and sometimes it works days - or even
>weeks - without any problem.
>
>The bug only appears during tape I/O (regardless of which tape program is
>used: btape, dd or tar).
>In most cases the tape write ends with an input/output error. After this
>error occurred, any access to the tape library robot (connected through
>the SAS interface of the first drive) fails:
>
># mtx unload 1 1
>Unloading drive 1 into Storage Element 1...mtx: Request Sense: Long Report=yes
>mtx: Request Sense: Valid Residual=no
>mtx: Request Sense: Error Code=70 (Current)
>mtx: Request Sense: Sense Key=Illegal Request
>mtx: Request Sense: FileMark=no
>mtx: Request Sense: EOM=no
>mtx: Request Sense: ILI=no
>mtx: Request Sense: Additional Sense Code = 53
>mtx: Request Sense: Additional Sense Qualifier = 01
>mtx: Request Sense: BPV=no
>mtx: Request Sense: Error in CDB=no
>mtx: Request Sense: SKSV=no
>MOVE MEDIUM from Element Address 257 to 4096 Failed
>
>After resetting the scsi bus (echo "- - -" >
>/sys/class/scsi_host/host5/scan) the tape drives are revitalized, but
>the changer device disappears. Even after a cold restart of the whole
>library the device keeps missing.
>
>Yet another problem: restting the SCSI bus of the LSI SAS HBA sometimes
>results in a hardy freeze (console stuck; no log messages).
>
>> [...]
>>
>>I do not believe it's a hardware fault at the moment as the machine
>>ran OK under Solaris for a few weeks (including successful btape runs).
>>
>
>The very same piece of hardware worked fine using Solaris 10 with heavy
>disk and tape I/O at the same time for two months.
>
>We really prefer using Linux instead, but we're in pressure of time.
>
>
>We appreciate any help resolving this bug!
>
>
>
>
>Regards,
>Sascha Frey
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2009-11-17 14:22 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 [this message]
2009-11-18  4:54       ` Desai, Kashyap
2009-11-18 13:39         ` Lukas Kolbe
2009-11-19  5:13           ` Desai, Kashyap
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=20091117142242.GA15638@TechFak.Uni-Bielefeld.DE \
    --to=lkolbe@techfak.uni-bielefeld.de \
    --cc=Kashyap.Desai@lsi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=support@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.