[stgt] Why "Microsoft iscsi" cannot work well with stgt (but it worked well with ietd)?
crquan at gmail.com
Thu Feb 12 17:57:16 CET 2009
On Thu, Feb 12, 2009 at 6:22 PM, Albert Pauw <albert.pauw at gmail.com> wrote:
> I believe that LUN 0 for the controller is more or less hardcoded.
> Yes, I have noticed this over a year ago and reported it here, I think.
I've compared and found the difference between ietd and tgtd:
1. ietd returned "REPORT LUN (0xa0)" with only 1 LUN (LUN id 1, Type Disk),
while tgtd report 2 LUNs, tgtd has the LUN 0 with "IET SCSI Controller"
as the first LUN (LUN id 0), and "LUN 1" Type Disk;
Since ietd reported only 1 LUN that worked well, why tgtd should
report the superfluous
"IET SCSI Controller" as the "LUN 0"? Why the "LUN 0" cannot be
deleted with tgtadm?
Cheng Renquan, Shenzhen, China
Doug Larson - "Instead of giving a politician the keys to the city,
it might be better to change the locks."
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the stgt