> If you did it WITHOUT blacklisting and succeed, I need
> to dig into the scsi code and check if the meaning of the flag
> is somehow treated in a reverse manner or whatever.
>
Well, I was looking through scsi.c to see what all those device flags
mean. I got to a part where it says:
/*
* If we want to only allow I/O to one of the luns attached to this device
* at a time, then we set this flag.
*/
if (bflags & BLIST_SINGLELUN)
SDpnt->single_lun = 1;
Should I interpret this that the SINGLELUN flag means "only talk to one
LUN at a time"? Maybe this is part of the problem, since your problems
begin when doing simultaneous access...
How do you know if a device can only handle a single lun communication
at a time? A lot of the devices "with special flags" have SINGLELUN
enabled. How is this determined? What is the effect on the usability?
As for my "5 LUNS" problem, Eric said there already was a MAX5LUN
employed for some Regal device. Is this the hack that avoids having
to specify "max_scsi_luns=5" in the boot prompt?
/*
* REGAL CDC-4X: avoid hang after LUN 4
*/
if (bflags & BLIST_MAX5LUN) {
*max_dev_lun = 5;
return 1;
}
Looks like a hack, but some devices call for a hack!
Brendan
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
