On 02/03/2012 05:45 AM, Евгений Мартынов wrote: >> After the initiator logs in, it asks the scsi layer to find scsi >> devices. The scsi layer does a inquiry to LUN 0, then will do a >> REPORT_LUNs command. The target then will tell is the LUNs and the scsi >> layer will add them. >> > > Yes, it works, thank you. I just add LUN0 to taget. > > Another Q: > > Is it really necessary to use LUN 0 to do all this operations? Is
Yeah. I think it is a scsi spec issue/requirement. > there the way to override this behavior and send REPORT LUNs command > without any LUN connected (to bus/host)? > > >> Note that the default max lun value iscsi_tcp supports is 512. This can >> be overridden by doing using the iscsi_tcp max_lun modparam "modinfo >> iscsi_tcp" for info. >> >> modparam iscsi_tcp max_lun=whatever_value_you_want. >> >> or you can do >> >> echo X > /sys/module/iscsi_tcp/paramters/max_lun >> >> before you run the login command. > > Seems to read only value for me. Ah you are right. I never turned on write support through sysfs. This has not come up very often. I will send a patch to fix it up. > But adding "options iscsi_tcp max_lun=16383" to modprobe.conf works > fine. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
