Bug 121676

Summary: [iscsi] iscontrol do not connect iscsi-target on sparc64
Product: Base System Reporter: SANAGI Terumasa <etherforet>
Component: sparc64Assignee: freebsd-scsi (Nobody) <scsi>
Status: Closed FIXED    
Severity: Affects Only Me CC: mmoll
Priority: Normal    
Version: 7.0-RELEASE   
Hardware: Any   
OS: Any   

Description SANAGI Terumasa 2008-03-13 20:50:04 UTC 
I tested ports/net/iscsi-target with /sbin/iscontrol and
Microsoft iSCSI Initiator.

These four boxes are,

1)ports/net/iscsi-target on FreeBSD i386
2)/sbin/iscontrol on FreeBSD i386
3)Microsoft iSCSI Initiator on WinXP i386
4)/sbin/iscontrol on FreeBSD sparc64

iscontrol setting is standard and discovery mode run.
2) and 3) run as normally connect successful.
but, bump errors 4).

ports/net/iscsi-target(i386) say,

pid 1829:iscsi.c:577: ***ERROR*** Bad "Byte 1, bits 2-3": Got 1 expected 0.
pid 1829:target.c:789: ***ERROR*** iscsi_login_cmd_decap() failed
pid 1829:target.c:1148: ***ERROR*** login_command_t() failed
pid 1829:target.c:1268: ***ERROR*** execute_t() failed

How-To-Repeat: # -- iscontrol sparc64 settings -- #
> cat /etc/iscsi.conf
port    = 3260
target0 {
        targetaddress   = 192.168.0.1 # your target IP/hostname
        targetname      = iqn.1994-04.org.netbsd.iscsi-target:target0
}
# -- sparc64 box iscsi.conf over -- #

# -- i386 |sparc64 box iscsi-target settings -- #
> cat /usr/local/etc/iscsi/targets
extent0         /tmp/iscsi-target0      0       1MB
target0                rw      extent0         192.168.0.0/24 # your target network address and/or mask
# -- i386 box targets over -- #

# /usr/local/bin/iscsi-t arget -f /usr/local/etc/iscsi/targets -D

# not fork run debugging
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-04-14 05:19:42 UTC 
Responsible Changed
From-To: freebsd-sparc64->freebsd-scsi

Reclassify.
Comment 2 seanwbruno 2013-04-15 13:47:11 UTC 
the iscsi tools and service have been updated in stable/9

Can you retest and verify that this is still an issue?  I don't see
these issues when running on 9.1R either.

Sean
Comment 3 sean_bruno 2013-05-07 17:59:00 UTC 
Confirmed still broken.

For now, I propose removing iscsi(4) from non-x86 architectures while we
await improved iscsi support in FreeBSD.

Sean

ref.   http://people.freebsd.org/~sbruno/iscsi_x86_only.txt
Comment 4 Michael Moll freebsd_committer freebsd_triage 2015-11-30 21:40:38 UTC 
Tested the iscsi initiator on a fresh CURRENT against a CTL LUN  and everything works as expected now. BTW, it also works for me on armv6hf, which is also non-x86.