Date: Mon, 16 Mar 2026 23:56:55 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Alan Somers <asomers@freebsd.org> Cc: Garrett Wollman <wollman@bimajority.org>, freebsd-stable@freebsd.org Subject: Re: ZFS deadlocks/memory accounting issues Message-ID: <abh8p9YG1qGVmTR_@kib.kiev.ua> In-Reply-To: <CAOtMX2gpNQH9hpCnRP%2Bm5kBJDMf5O3MSHgzPVjBKEObyL8bjdw@mail.gmail.com> References: <27064.27391.224476.910636@hergotha.csail.mit.edu> <CAOtMX2gpNQH9hpCnRP%2Bm5kBJDMf5O3MSHgzPVjBKEObyL8bjdw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Mon, Mar 16, 2026 at 03:08:44PM -0600, Alan Somers wrote: > I once saw a similar bug. In my case I had a process that mmap()ed > some very large files on fusefs, consuming lots of inactive pages. > And when the system comes under memory pressure, it asks ARC to evict > first. So the ARC would end up shrinking down to arc_min every time. > In my case, the solution was to set vfs.fusefs.data_cache_mode=0 . I > suspect that similar bugs could be possible with UFS or tmpfs, if they > have giant files that are mmaped(). What are 'similar bugs with UFS or tmpfs'? Can you please be more specific, what is the erronous behavior?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?abh8p9YG1qGVmTR_>