Re: kern/58422: kernel crash when using the iscsi initiator

[mlelstv%serpens.de@localhost (Michael van Elst)]

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

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/58422: kernel crash when using the iscsi initiator
Date: Sat, 27 Jul 2024 20:26:07 -0000 (UTC)

 6bone%6bone.informatik.uni-leipzig.de@localhost writes:
 
 >[ 95512.393054] Received Reject PDU, reason = 4, data_len = 48
 >[ 95512.393054] S3C1: *** Connection Error, status=25, logout=1, state=3
 
 Protocol error (status=25)
 
 Maybe your iscsi target can tell more.
 
 
 >[ 95512.393054] sd3(iscsi0:0:0:11): generic HBA error
 >[ 95512.393054] sd3d: error writing fsbn 34674059682 of 34674059682-34674059745 (sd3 bn 34674059682; cn 16930693 tn 13 sn 2)
 >[ 95519.402427] sd3d: error writing fsbn 35353610530 of 35353610530-35353610593 (sd3 bn 35353610530; cn 17262505 tn 9 sn 2)
 
 As the result some pending I/Os get aborted.
 
 
 >[ 95522.475421] S3C1: *** Connection Error, status=24, logout=-1, state=5
 
 Timeout (status=24)
 
 
 >[ 95524.408023] sd3d: error reading fsbn 33006352546 of 33006352546-33006352609 (sd3 bn 33006352546; cn 16116383 tn 5 sn 2)
 
 Another I/O error as consequence.
 
 
 >[ 95524.498026] S3C1: Resend ccb 0xffffc280676b72b8 (37) - updating CmdSN old 21405452, new 21405454
 >[ 95524.498026] S3C1: Connection ReCreated successfully - status 0
 
 iscsi recovers, but the result is like with any failing disk.
 
 
 >[ 95525.691696] panic: ufsdirhash_findfree: free mismatch
 
 The filesystem crashes for some inconsistent data on the drive.