Date: Fri, 8 Apr 2022 17:02:24 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= <roger.pau@citrix.com> To: Ze Dupsys <zedupsys@gmail.com> Cc: <freebsd-xen@freebsd.org>, <buhrow@nfbcal.org> Subject: Re: ZFS + FreeBSD XEN dom0 panic Message-ID: <YlBOgFYNokZ0rTgD@Air-de-Roger> In-Reply-To: <209c9b7c-4b4b-7fe3-6e73-d2a0dc651c19@gmail.com> References: <Yj16hdrxawD61mAL@Air-de-Roger> <639f7ce0-8a07-884c-c1cf-8257b9f3d9e8@gmail.com> <Yj7YrW9CG2aXT%2BiC@Air-de-Roger> <4da2302b-0745-ea1d-c868-5a8a5fc66b18@gmail.com> <Yj8lZWqeHbD%2BkfOQ@Air-de-Roger> <48b74c39-abb3-0a3e-91a8-b5ab1e1223ce@gmail.com> <YkAqxjiMM1M1QdgR@Air-de-Roger> <22643831-70d3-5a3e-f973-fb80957e80dc@gmail.com> <Ykxev3fangqRGQcn@Air-de-Roger> <209c9b7c-4b4b-7fe3-6e73-d2a0dc651c19@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 08, 2022 at 10:45:12AM +0300, Ze Dupsys wrote: > On 2022.04.05. 18:22, Roger Pau Monné wrote: > > .. Thanks, sorry for the late reply, somehow the message slip. > > > > I've been able to get the file:line for those, and the trace is kind > > of weird, I'm not sure I know what's going on TBH. It seems to me the > > backend instance got freed while being in the process of connecting. > > > > I've made some changes, that might mitigate this, but having not a > > clear understanding of what's going on makes this harder. > > > > I've pushed the changes to: > > > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/for-leak > > > > (This is on top of main branch). > > > > I'm also attaching the two patches on this email. > > > > Let me know if those make a difference to stabilize the system. > > Hi, > > Yes, it stabilizes the system, but there is still a memleak somewhere, i > think. > > System could run tests for approximately 41 hour, did not panic, but started > to OOM kill everything. > > I did not know how to git clone given commit, thus i just applied patches to > 13.0-RELEASE sources. > > Serial logs have nothing unusual, just that at some point OOM kill starts. Well, I think that's good^W better than before. Thanks again for all the testing. It might be helpful now to start dumping `vmstat -m` periodically while running the stress tests. As there are (hopefully) no more panics now vmstat might report us what subsystem is hogging the memory. It's possible it's blkback (again). Thanks, Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YlBOgFYNokZ0rTgD>