[stgt] Why "Microsoft iscsi" cannot work well with stgt (but it worked well with ietd)?
crquan at gmail.com
Fri Feb 13 02:12:26 CET 2009
On Fri, Feb 13, 2009 at 1:03 AM, Richard Sharpe
<realrichardsharpe at gmail.com> wrote:
> On 2/12/09, Cheng Renquan <crquan at gmail.com> wrote:
>> 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?
> Hmmm, would SCST also work for you?
I will try later, but currently is there someone who can configure
windows and stgt co-work well?
> What sort of device are you trying to develop?
> Richard Sharpe
Cheng Renquan, Shenzhen, China
Marlene Dietrich - "Most women set out to try to change a man, and
when they have changed him they do not like h...
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