That's strange. I have no useful input, but I'm simply chiming in to state
that we have much larger than 2TB iSCSI LUNs working fine, under CentOS 5.x
here. I can't imagine CentOS 6.x would regress in that manner.
The only time I've seen something similar (especially the 0 byte size
export) is
The iSCSI initiator layer does not control/manage this. It looks like it might
be a target issue since we see both the scsi layer and sg utile reporting zero
logical blocks.
Are you using SCST for the target, or did you buy a target from some vendor
that is using SCST?
On Dec 30, 2012, at
Yes! I by I have Segate Blackarmor Nas 440 4x2TB HD in raid 5
Do you think that this is it does not give me the Lun's is greater than 2TB?
How this can be verified by the initiator (client) ?
i have sg utils and iscsiadm
2012/12/31 Michael Christie micha...@cs.wisc.edu
The iSCSI initiator
I am not sure what you are asking. You should contact your target vendor.
Take a tcpdump or wireshark trace when you login to the target or when
you do the sg_reacap 16 command.
So do something like
tcpdump -w iscsi.out -i your_ethX
iscsiadm -m node -T yourtarget -p ip -l
Then send the
I have Segate Blackarmor 440 4x2TB HD in raid 5
i create ISCSI device
5493 GB 0 Full Access
service iscsi start
iscsiadm -m discovery -t st -p 192.168.0.2
fdisk -l no see new disk
dmesg
scsi5 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access SCST_FIO BZ 200 PQ: 0 ANSI: 5
sd
