Date: Tue, 20 Dec 2022 00:10:05 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 266302] [zfs][iscsi] Periodic drops by ctl with "failed to allocate soft PDU" since 13.1 Message-ID: <bug-266302-3630-QMfSImBun0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266302-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-266302-3630@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=3D266302 --- Comment #2 from eborisch+FreeBSD@gmail.com --- What's interesting is that, in the latest one I have data for, the free mem= ory never fell below 10GB. (Granted, that is only being sampled every 30s in my logging, so it could have much lower briefly.) I see a spike (monitoring vmstat -z) of a large number of frees just after = the error was detected -- abd_chunk, zio_buf_comb_131072, and dnode_t being the largest, freeing a combined 2.2GB, and a spike in failures for 'vm pgcache' immediately before it, and continuing immediately after the failure. I've p= ut a copy of the logging (1m) of vmstat -z and some analysis here: https://github.com/eborisch/pdu-error/blob/main/pdu_analysis.ipynb The log stops _after_ the error was detected, so it has considerable data leading up to, and then one data point after an instance of this error, if you're interested in looking at it. In the interim, I can further restrict vfs.zfs.arc_max; I already have it s= et to 75% of the 64GB system. --=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-266302-3630-QMfSImBun0>