From owner-freebsd-fs@FreeBSD.ORG Wed May 11 10:37:14 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A016E1065672 for ; Wed, 11 May 2011 10:37:14 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 29FD48FC14 for ; Wed, 11 May 2011 10:37:13 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id p4BAb3P6048487 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 11 May 2011 13:37:08 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4DCA66CF.7070608@digsys.bg> Date: Wed, 11 May 2011 13:37:03 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4DCA5620.1030203@dannysplace.net> <20110511100655.GA35129@icarus.home.lan> In-Reply-To: <20110511100655.GA35129@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS: How to enable cache and logs. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2011 10:37:14 -0000 On 11.05.11 13:06, Jeremy Chadwick wrote: > On Wed, May 11, 2011 at 07:25:52PM +1000, Danny Carroll wrote: >> When I move to v28 I will probably wish to enable a L2Arc and also >> perhaps dedicated log devices. >> > In the case of ZFS intent logs, you definitely want a mirror. If you > have a single log device, loss of that device can/will result in full > data loss of the pool which makes use of the log device. This is true for v15 pools, not true for v28 pools. In ZFS v28 you can remove log devices and in the case of sudden loss of log device (or whatever) roll back the pool to a 'good' state. Therefore, for most installations single log device might be sufficient. If you value your data, you will of course use mirrored log devices, possibly in hot-swap configuration and .. have a backup :) By the way, the SLOG (separate LOG) does not have to be SSD at all. Separate rotating disk(s) will also suffice -- it all depends on the type of workload. SSDs are better, for the higher end, because of the low latency (but not all SSDs are low latency when writing!). The idea of the SLOG is to separate the ZIL records from the main data pool. ZIL records are small, even smaller in v28, but will cause unnecessary head movements if kept in the main pool. The SLOG is "write once, read on failure" media and is written sequentially. Almost all current HDDs offer reasonable sequential write performance for small to medium pools. The L2ARC needs to be fast reading SSD. It is populated slowly, few MB/sec so there is no point to have fast and high-bandwidth write-optimized SSD. The benefit from L2ARC is the low latency. Sort of slower RAM. It is bad idea to use the same SSD for both SLOG and L2ARC, because most SSDs behave poorly if you present them with high read and high write loads. More expensive units might behave, but then... if you pay few k$ for a SSD, you know what you need :) Daniel