From owner-freebsd-stable@FreeBSD.ORG Mon Feb 16 00:30:51 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70456FCC for ; Mon, 16 Feb 2015 00:30:51 +0000 (UTC) Received: from j006.host001.searchy.nl (j006.host001.searchy.nl [79.143.214.199]) by mx1.freebsd.org (Postfix) with ESMTP id 35A82CDE for ; Mon, 16 Feb 2015 00:30:50 +0000 (UTC) Received: from [192.168.5.21] (5418287B.cm-5-1a.dynamic.ziggo.nl [84.24.40.123]) (Authenticated sender: ppi@j006.host001.searchy.nl) by j006.host001.searchy.nl (Postfix) with ESMTPSA id 826461E8C1F for ; Mon, 16 Feb 2015 00:23:40 +0000 (UTC) Message-ID: <54E1388C.3060602@searchy.net> Date: Mon, 16 Feb 2015 01:23:40 +0100 From: "Frank de Bot (lists)" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: ZFS L2arc 16.0E size Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 00:30:51 -0000 Hello, I have a FreeBSD 10.1 system with a raidz2 zfs configuration with 2ssd's for l2arc . It is running '10.1-STABLE FreeBSD 10.1-STABLE #0 r278805' Currently I'm running tests before it can go to production, but I have the following issue. After a while the l2arc devices indicate 16.0E free space and it starts 'consuming' more than it can hold cache - - - - - - gpt/l2arc1 107G 16.0E 0 2 0 92.7K gpt/l2arc2 68.3G 16.0E 0 1 0 60.8K It ran good for a while, where data was removed from cache so it could be filled with newer data. (Free space was always around 200/300Mbytes). I've read about similar issues, which should be fixed in different commits, but I'm running the latest stable 10.1 kernel right now. (One of the last similar issue is: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197164 ) Another similar issue reported at FreeNAS https://bugs.freenas.org/issues/5347 suggested it would be a hardware issue, but I have 2 servers which experience the same problem. One has a Crucial M500 drive and the other a M550. Both have a 64G partition voor l2arc. What is really going on here? Regards, Frank de Bot