Date: Fri, 22 Oct 2021 07:55:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 259152] [iscsi] OCI oracle iscsi block device problems Message-ID: <bug-259152-227-rMtRfRWDrm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259152-227@https.bugs.freebsd.org/bugzilla/> References: <bug-259152-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259152 --- Comment #14 from Dave Cottlehuber <dch@freebsd.org> --- Created attachment 228938 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D228938&action= =3Dedit iscsid: default conn_max_recv_data_segment_length to our request Author: Ed Maste <emaste@FreeBSD.org> Date: Thu Oct 21 11:09:58 2021 -0400 iscsid: default conn_max_recv_data_segment_length to our request XXX attempted workaround for PR259152; target did not respond with MaxRecvDataSegmentLength and so we did not update conn_max_recv_data_segment_length. PR: 259152 Ed's patch here "works for me" - I can see, mount, & use iscsi targets on b= oth VM and BM now, handling a full 20GiB zpool resilver between volumes without issue. I expect we'll survive a buildworld as well. My understanding is that we have several "wip patches" that need somebody w= ho's more familiar with the spec and the code to make a call if this is (a) appropriate and (b) if patches need to evolve further to commit to main. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259152-227-rMtRfRWDrm>