Date: Wed, 14 Jul 2010 11:26:08 +0200 From: Martin Matuska <mm@FreeBSD.org> To: Peter Jeremy <peterjeremy@acm.org> Cc: freebsd-current@FreeBSD.org Subject: Re: [CFT] ZFS v15 patch (version 3) Message-ID: <4C3D82B0.1010907@FreeBSD.org> In-Reply-To: <20100714082346.GA95442@server.vk2pj.dyndns.org> References: <4C31C71C.2010606@FreeBSD.org> <20100708200446.GA33822@server.vk2pj.dyndns.org> <4C364379.6020608@FreeBSD.org> <20100714001423.GA92530@server.vk2pj.dyndns.org> <4C3D6439.3010702@FreeBSD.org> <20100714082346.GA95442@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In other words: The problem is not caused by head-12636.patch And this is important, otherwise we are seeking for an error where it isn't. I know about the current ARC problem and we have to seek a reasonable solution for it, but no ugly hacks that work only in specific cases / workloads. Dňa 14. 7. 2010 10:23, Peter Jeremy wrote / napísal(a): > On 2010-Jul-14 09:16:09 +0200, Martin Matuska <mm@FreeBSD.org> wrote: >> Without head-12636.patch you are unable to reproduce the deadlock? > The deadlock occurs with either stock 8-stable or with head-12636.patch. > > I have also been testing arc.patch2 from > http://lists.freebsd.org/pipermail/freebsd-stable/2010-July/057696.html > I am unable to reproduce the deadlock when using the combination of > arc.patch2 and head-12636.patch but have not yet tested arc.patch2 alone. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C3D82B0.1010907>