Robert Frey wrote:
>
> "Justin T. Gibbs" wrote:
>
> > I agree with all that you've said, but you've left out the most compelling
> > reason that domain validation is necessary: SCSI->SCSI bridges. Although
> > a SCSI-SCSI bridge may support some LVD transfer speeds, it may not support
> > all of them. The only way to find out is to perform domain validation.
> > For instance, I have no idea if the currently available LVD->SE/LVD bridges
> > understand DT transfers.
>
> That's a good point along with Dan's legacy SCSI backplane example. But I can
> argue this is a misconfiguration.
OK, this has gone beyond a usefull debate. If you want to take the high road
that anything other than a perfectly sculpted SCSI bus that does everything
perfectly is a misconfiguration, and that no external factors are allowed to
influence the SCSI bus, and that everyone must buy matched hardware all at one
time instead of upgrading piecemeal, etc., then feel free. I, on the other
hand, have to worry about all the times that users email me with problems that
*I* know are SCSI bus related problems (termination, cable length, cable type,
cable proximity to other emf producing devices such as active IDE cables,
backplanes that don't grok the latest signals but do at least know LVD and
could therefore be a cause of problems with DT transfers, etc) but that take
their system down. If even one of those users is kept running long enough
that the problem *isn't* an "I'm dead in the water, save me!" issue and
instead they can limp by, then that means I'm not busting my ass having to
take care of it on their time scale. That's what matters to me. And to date,
there have already been multiple cases of this being true where the system
backed all the way down to async mode as needed, but at least it kept running
and I could help them solve their problem as *I* had time to do it.
--
Doug Ledford <[EMAIL PROTECTED]> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
