Re: kern/46896: iSCSI initiator ccb_pool gets corrupted

["Michael L. Hitch" <mhitch%lightning.msu.montana.edu@localhost>]

The following reply was made to PR kern/46896; it has been noted by GNATS.

From: "Michael L. Hitch" <mhitch%lightning.msu.montana.edu@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/46896: iSCSI initiator ccb_pool gets corrupted
Date: Tue, 11 Sep 2012 08:51:34 -0600 (MDT)

 > Found it!  And it was a bug introduced when I updated.
 >
 > An update by mlelstv had included an extraneous change that had been an
 > earlier attempt by me to fix a system freeze when writing > 64K. I had
 > done my fix differently when I commited my changes, but mlelstv's change
 > still had that.  That error was causing the ccb to not be added to the
 > ccbs_waiting queue properly..
 
    Unfortunately, this just changes to failure to something else.  After 
 running a while, I eventually get messages (with ISCSI_DEBUG 1):
 
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676370, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676371, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676372, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676373, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676374, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676375, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676376, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676377, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676378, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676379, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676380, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676381, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676382, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676383, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676384, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676385, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676386, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676387, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676388, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676389, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676390, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676391, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676392, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676393, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676394, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676395, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676396, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676397, ExpCmdSn=676369
   /netbsd: S2C1: CheckCmdSN resending - CmdSN=676398, ExpCmdSn=676369
   /netbsd: Received Reject PDU, reason = 4, data_len = 48
   /netbsd: Received Asynch PDU, Event 1
   /netbsd: ISCSI: kill_session 2, status 44, logout 0, recover 0
   /netbsd: S2C1: Write failed sock 0xffffa00003471420 (ret: 32, req: 48, 
 resid: 48)
   /netbsd: S2C1: *** Connection Error, status=18, logout=-1, state=3
   /netbsd: S2C1: Kill_connection: terminating=0, status=18, logout=-1, 
 state=3
   /netbsd: Session 2 not found
 
    I'm looking at an alternative method of resolving this.
 
 --
 Michael L. Hitch                       mhitch%montana.edu@localhost
 Computer Consultant
 Information Technology Center
 Montana State University       Bozeman, MT     USA