James, I have a contract and have requested the fix.
Jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 5:54 AM To: Jim Barker; Eric Hill Cc: [email protected] Subject: Re: [storage-discuss] Windows iSCSI Client Crashing During File Copy > FYI: Sun has this bug documented, below is an excerpt.... > > Thanks for the information which shows the problem. > > I can now reach the URL OK. Indeed the snoop shows the problem that is > detailed in that thread in that when the NOP-IN is sent, the StatSN is > incremented (in error). The initiator will see this as an error as > it's ExpStatSN is lower than this. > > Looking into SunSolve wee see this logged as CR 6521425 " ...When > sending a NOP-In message the statsn value should not be > incremented.... > > CR 6521425 is documented as being fixed in Nevada60 On Jan 16, 2008, at 3:35 PM, Eric Hill wrote: I'm running Solaris 10 update 8/07. On Jan 24, 2008, at 3:02 PM, Jim Barker wrote: I am running Solaris 10 Update 4 Although the defect has been fixed in Nevada Build 60, to date, no customer with a support contract on Solaris 10 has requested this fix. Therefore no plans are in place to fix the defect in the next update of S10, or to generate a patch for prior updates. > This message posted from opensolaris.org > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss Jim Dunham Storage Platform Software Group Sun Microsystems, Inc. _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
