From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 12:16:47 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6DBE1065672 for ; Thu, 7 Apr 2011 12:16:47 +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 373F28FC1E for ; Thu, 7 Apr 2011 12:16:46 +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 p37CGanp017038 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 7 Apr 2011 15:16:42 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4D9DAB24.1050707@digsys.bg> Date: Thu, 07 Apr 2011 15:16:36 +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: Pete French References: In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ZFS HAST config preference X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2011 12:16:47 -0000 On 06.04.11 15:55, Pete French wrote: > Or, I could use ZFS volumes and run HAST on top of these. This means, >> that on each blade, I will have an local ZFS pool. Let's call this setup2. > ...you would need to put a filesystem on to of the > HAST filesystem though, what would that be ? Thanks for your comments Pete. The idea here is to have local ZFS pool(s) on each of the nodes. Then, in each local ZFS pool create ZFS volumes and use these for HAST. On the HAST device, I would again run ZFS, just without any redundancy. Just to avoid having to run fsck after switching roles. This should, I guess, permit safe use of cache and log devices for pools, thus increasing performance. However, no idea how reliability will be affected if sudden loss of one node happens, especially the active node. It seems I am going with setup1 for now, going live in about a week. Daniel