OK - Thanks for the Info.
For the moment, the machine in question will be simply running as a SAMBA
Server, and then only for one or two clients at a time (it's storing disk
images from PowerQuest's Drive Image Pro Software), and it (so far) seems to
be stable enough when data is coming in from the network.
If there is any detailed info. I can give you from the system, I'll be happy
to pop them over to you - similarly, if I can help test any revised versions
in the future, I'd be happy to do so.
Thanks again... :)
On Thursday 25 July 2002 13:25, Andre Hedrick wrote:
> The oddities are the fact I have not finished creating the channel and
> drive set inner-lock sequence code :-/ If you run it in master mode only
> one drive per channel, it is perfectly safe. The problem happens the
> instant you pair drives on the channels. I have not figured out the
> correct interrupt sequence ordering and blocking recipe.
>
> The issue stands to deal with double hwgroups locking and having more than
> two channels to the effective HBA.
>
> Instead of
>
> HPT374
> ide4
> ide5
> HPT374
> ide6
> ide7
>
> It has to evlolve to
>
> HPT374
> ide4p
> ide4s
> ide5p
> ide5s
>
> This means extened minor on the second half of each major must be created.
> There is not enough sane bandwith in the driver, nor would anybody take
> such an exotic solution.
>
> Sorry,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 30 2002 - 14:00:19 EST