Issues with 9.10 FiberChannel ISCSI

Status
Not open for further replies.

Ellusionist

Dabbler
Joined
Jul 22, 2014
Messages
20
Just want to check on this. After upgrading to 9.10 from 9.3.

I'm getting the follow error on the screen after... Once it happens even a reboot will not correct the issue unless you power down the system and restart.

isp_target_put_entry: Request Queue Overflow

Seems as though the iscsi target have ceased also... 9.3 seemed to be working.. Any major changes to Fiber Channel and iscsi within Freenas 9.10?

Thoughts?
 
D

dlavigne

Guest
Any major changes to Fiber Channel and iscsi within Freenas 9.10?

Yup, the OS went from FreeBSD 9-STABLE to FreeBSD 10-STABLE.

If you decide to make a bug report at bugs.freenas.org, include a debug in the ticket (made from System -> Advanced -> Save Debug), and post the issue number here.
 

Ellusionist

Dabbler
Joined
Jul 22, 2014
Messages
20
Created the ticket. Going to start troubleshooting on this end. Not to familiar with testing from the command line for HBA FC with iscsi...

[root@nas2 /]# ctladm port -l

Port Online Frontend Name pp vp

0 YES tpc tpc 0 0
1 NO camsim camsim 0 0 naa.5000000fcdd40702
2 YES ioctl ioctl 0 0
3 YES camtgt isp0 0 0 naa.21000024ff5ebccc
4 YES camtgt isp1 0 0 naa.21000024ff5ebccd
5 YES iscsi iscsi 257 1 iqn.2011-03.org.example.istgt:esx,t,0x0101

[root@nas2 /]# ctladm devlist

LUN Backend Size (Blocks) BS Serial Number Device ID

0 block 6442450944 512 002590ebc8ec001 iSCSI Disk 002590ebc8ec001

[root@nas2 /]#
 

Ellusionist

Dabbler
Joined
Jul 22, 2014
Messages
20
Any tips for troubleshooting iscsi issues? LUN's keep coming up and disappearing from ESX. Going to probably roll back since I saved the config from before on 9.3...
 

Ellusionist

Dabbler
Joined
Jul 22, 2014
Messages
20
Looks like the ESX side is causing this when the datastore is rescanned? Going to have to roll back to 9.3.
 

Ellusionist

Dabbler
Joined
Jul 22, 2014
Messages
20
Rolled back to 9.3 and restored the config. ESX picked up the data-stores without an issue. Along with no errors on the Freenas side.
 
Status
Not open for further replies.
Top