From owner-freebsd-current@FreeBSD.ORG  Tue Feb 11 14:00:24 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E7B4CF9E
 for <freebsd-current@FreeBSD.org>; Tue, 11 Feb 2014 14:00:24 +0000 (UTC)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 35852156E
 for <freebsd-current@FreeBSD.org>; Tue, 11 Feb 2014 14:00:22 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA08144;
 Tue, 11 Feb 2014 16:00:20 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1WDDsp-000ALL-Nx; Tue, 11 Feb 2014 16:00:19 +0200
Message-ID: <52FA2CA2.5000508@FreeBSD.org>
Date: Tue, 11 Feb 2014 15:58:58 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Vitalij Satanivskij <satan@ukr.net>
Subject: Re: ARC "pressured out", how to control/stabilize ? (reformatted
 to text/plain)
References: <52D66DB6.7030807@FreeBSD.org>
 <1390900795.258244476.v35k1338@frv45.ukr.net> <52EA3459.3070300@FreeBSD.org>
 <1391083826.948700370.cmzf8475@frv45.ukr.net>
 <20140131182637.GA82526@hell.ukr.net> <20140204100823.GA95709@hell.ukr.net>
 <52F0F687.6050307@FreeBSD.org> <20140204171040.GA82996@hell.ukr.net>
 <52F12210.10604@FreeBSD.org> <20140205090449.GA9341@hell.ukr.net>
 <20140205122241.GA38114@hell.ukr.net> <52F4A35E.1080902@FreeBSD.org>
In-Reply-To: <52F4A35E.1080902@FreeBSD.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Vladimir Sharun <atz@ukr.net>,
 Current FreeBSD <freebsd-current@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2014 14:00:25 -0000

on 07/02/2014 11:11 Andriy Gapon said the following:
> on 05/02/2014 14:22 Vitalij Satanivskij said the following:
>> Dear Andriy and FreeBSD community,
>>
>> Ok. I'm get coredump on panic.
>>
>> What else i need to do?
> 
> 
> Vitalij, Vladimir,
> 
> I have been able to reproduce the leak at work, so now I have full access to all
> debugging information that I need.  Thank you for your testing and reports.
> 
> I have reported my observations to OpenZFS developers.  It looks like the author
> of L2ARC compression code is too busy right now to produce a fix.
> Unfortunately, I am not very familiar with the L2ARC code, so I can not promise
> to produce a patch soon.

I've been able to spend some time on this issue.
Could you please try the following patch?
http://people.freebsd.org/~avg/l2arc-b_tmp_cdata-diag.2.patch
It obsoletes all previous patches from me.

-- 
Andriy Gapon