I have used stgt's iSCSI functionality: 1. start tgtd; 2. use tgtadm add a new target, add a lun with backing store /dev/sdb5, add ACL information; then it looks like: root at uitnode1 ~/tmp/tgt-trunk-20090210 0 # usr/tgtadm --lld iscsi --mode target --op show Target 1: iqn.2007-10.com.uit:uit2-tui2 System information: Driver: iscsi State: ready I_T nexus information: LUN information: LUN: 0 Type: controller SCSI ID: deadbeaf1:0 SCSI SN: beaf10 Size: 0 MB Online: Yes Removable media: No Backing store: No backing store LUN: 1 Type: disk SCSI ID: deadbeaf1:1 SCSI SN: beaf11 Size: 30006 MB Online: Yes Removable media: No Backing store: /dev/sdb5 Account information: ACL information: 172.16.97.201 172.16.100.65 open-iscsi can logon this target, while "Microsoft iSCSI initiator 2.08 (latest)" seems cannot; in fact not "microsoft iscsi" 's fault, but the windows system cannot recognize the "IET Controller SCSI Array Device"; I have searched on the Internet, and cannot find a windows driver for such a device; Furthermore, I compared the stgt iscsi and iet(iscsitarget.sf.net), I found that iscsitarget only serves "LUN 1" as Type disk, it doesn't provide a "LUN 0" with Type Controller, I tried to delete the "LUN 0 Type Controller" with tgtadm, but it seems not work: # usr/tgtadm --lld iscsi --mode logicalunit --op delete --tid 1 --lun=0 tgtadm: 'lun' option is necessary Appreantly I input with "--lun=0", but it seems not aware of that, why? Simply speaking, how can I make stgt work with microsoft iscsi? Or make windows work with stgt? Thanks, -- Cheng Renquan, Shenzhen, China Jay London - "My father would take me to the playground, and put me on mood swings." -- 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 |