[8205] in linux-scsi channel archive
Re: recovery behaviour with 1 bad + 1 good drive (aic7xxx)
daemon@ATHENA.MIT.EDU (Ricky Beam)
Thu Feb 24 01:12:12 2000
Date: Thu, 24 Feb 2000 01:01:49 -0500 (EST)
From: Ricky Beam <jfbeam@bluetopia.net>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <38B4C05D.6234D15A@redhat.com>
Message-ID: <Pine.LNX.4.04.10002240054400.12259-100000@beaker>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Thu, 24 Feb 2000, Doug Ledford wrote:
>> That list already exists (sortof) There's a list of drives with whom
>> drivers should not probe LUNs or attempt tagged queuing. I messed with it
>> once to allow queuing on my Jaz drive -- it was blcklisted but works just
>> fine. (only a few firmware versions have a problem; it's safer to always
>> say NO!)
>
>More than a few versions of Jaz drive have that bug, everything with a
>firmware version J.86 or earlier has that bug.
Yep. But the blist doesn't check the revision (or didn't) thus all jaz
drives end up with tag queuing disabled -- that's certainly the safe thing
to do. I hate the speed degradation... <grin>
Checking my machines:
(jakolantronic/alpha) Vendor: iomega Model: jaz 1GB Rev: G.72
(dominion/x86) Vendor: iomega Model: jaz 1GB Rev: J^77
(foobar/x86) Vendor: iomega Model: jaz 1GB Rev: J.83
All of those have an active queue depth of 8 and work perfectly. I have
a few other jaz drives not in an machines so I don't know their revisions,
but they work fine with a queue depth of 8 as well.
--Ricky
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
