Date: Mon, 6 Jan 2020 10:32:13 +0100 (CET) From: Wojciech Puchar <wojtek@puchar.net> To: Mark Millard <marklmi@yahoo.com> Cc: Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org Subject: Re: processes are killed because of out of swap space Message-ID: <alpine.BSF.2.20.2001061030350.27958@puchar.net> In-Reply-To: <B30C7C68-CFB7-4252-B114-BEC023501FC9@yahoo.com> References: <C1C8F724-88B0-49D9-A9DF-DB0AA8AF3164.ref@yahoo.com> <C1C8F724-88B0-49D9-A9DF-DB0AA8AF3164@yahoo.com> <alpine.BSF.2.20.2001051307080.18098@puchar.net> <alpine.BSF.2.20.2001051408100.3906@puchar.net> <9C6B115C-90CC-449D-A29D-429BD97F37C4@yahoo.com> <alpine.BSF.2.20.2001052139580.34061@puchar.net> <B30C7C68-CFB7-4252-B114-BEC023501FC9@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> context. > > If anyone is to work on geom_raid5, knowledge that: > > A) it was getting OOM kills that the other technique did not > and: > B) vm.pageout_oom_seq changes were controlling when > > likely would be useful background information. I > wonder if a bugzilla report of such would be > appropriate. (Some detail about the time frames > for the alternative vm.pageout_oom_seq figures might > be appropriate.) > > === geom_raid5 seems to be more buggy. I was aware that it write buffers data so in case of power loss there would be damage, but i've set 3 second maximum caching time and got huge destruction of underlaying filesystem (fsck displayed hundreds of thousands of errors).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.2001061030350.27958>