Date: Sat, 18 Dec 1999 01:31:34 +0200 From: Vallo Kallaste <vallo@matti.ee> To: Matthew Dillon <dillon@apollo.backplane.com> Subject: Re: Weird story with dump | restore Message-ID: <19991218013134.A1458@myhakas.matti.ee> In-Reply-To: <199912171918.LAA64133@apollo.backplane.com>; from Matthew Dillon on Fri, Dec 17, 1999 at 11:18:18AM -0800 References: <19991217123742.A70473@myhakas.matti.ee> <199912171648.IAA29595@gndrsh.dnsmgr.net> <19991217210227.A945@myhakas.matti.ee> <199912171918.LAA64133@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 17, 1999 at 11:18:18AM -0800, Matthew Dillon <dillon@apollo.backplane.com> wrote: > Try this patch to -current, it should solve the problem. I've been > meaning to fixup the buf_daemon for a while. This solves the > buf_daemon problem. We still will not be entirely optimal due to kvm > reshuffling but that's a different problem. Thank you for your clear explanation and patch, I will try it out. Your previous suggestion to lower the dirtybuffers marks was successful. The initial values were 222 for hi and 125 for lowmark. Lowering them by half let the restore run as usual. Now I'm running off from an IBM 35GB disk :-) that's because my response was abit delayed. Thanks -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991218013134.A1458>