From owner-freebsd-fs@FreeBSD.ORG Mon Mar 1 20:02:14 2010 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E125106566B for ; Mon, 1 Mar 2010 20:02:14 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-iw0-f183.google.com (mail-iw0-f183.google.com [209.85.223.183]) by mx1.freebsd.org (Postfix) with ESMTP id DD0358FC17 for ; Mon, 1 Mar 2010 20:02:13 +0000 (UTC) Received: by iwn13 with SMTP id 13so3254239iwn.14 for ; Mon, 01 Mar 2010 12:02:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=QcfcwY5e2K3ihRRqZioUAfjZTxHjPt9yD/FXWkfg/B0=; b=Gc51axVTreVnllwGxvHV+1/URZxl+Odra3u/uTRyzZsrGxSkT4KNtaVsiFBYd4CdQp cfEmNPNiJw9Gn6M8W/ZjAZXCUQrIIS0PRb0Vlgp/Zq18gZ6nj4926imRyIupEJjt1GvD x8iMtfQsMwt6N0GY2Rg3OzTx1nSO3s+A80zNo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RvLhysrU925/T/bybwsp2BR9UYvRws0su1BdQ69MyGRmzWGfTruaadXla6+PRDlPOV t3VaNlUvcdFyyCkEF9CsMyRy1r7pdsXrF85di5cKkjla+PCj4M9VOzp6MZX0UiZJu/N0 d4ZNuqAYsvnlA4vY2B5wc1ClfBdYn8U5G3fls= MIME-Version: 1.0 Received: by 10.231.170.136 with SMTP id d8mr148062ibz.17.1267473435166; Mon, 01 Mar 2010 11:57:15 -0800 (PST) Date: Mon, 1 Mar 2010 11:57:15 -0800 Message-ID: From: Freddie Cash To: fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: HAST, ucarp, and ZFS 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: Mon, 01 Mar 2010 20:02:14 -0000 Perhaps it's just a misunderstanding on my part of the layering involved, but I'm having an issue with the sample ucarp_up.sh script on the HAST wiki page. Here's the test setup that I have: hast1: glabel 4x 2 GB virtual disks (label/disk01 --> label/disk04) hast.conf create 4 resources (disk01 --> disk04, using the glabelled disks) zpool create hapool raidz1 hast/disk01 .. hast/disk04 hast2: glabel 4x 2 GB virtual disks (label/disk01 --> label/disk04) hast.conf create 4 resources (disk01 --> disk04) So far so good. On hast1, I have a working ZFS pool, I can create data, filessytems, etc, and watch network traffic as it syncs to hast2. I can manually down hast1 and switch hast2 to "primary" and import the hapool. I can create data, filesystems, etc. And I can manually bring hast1 online and set it to secondary, and watch it sync back. Where I'm stuck is how to modify the ucarp_up.sh script to work with multiple hast resources. Do I just edit it to handle each of the 4 hast resources in turn, or am I missing something simple, like that there should only be a single hast resource? I'm guess it's a simple "edit the script to suit my setup" issue, but wanted to double-check. The production server I want to use this with has 24 harddrives in it, configured into multiple raidz2 vdevs, as part of a single ZFS pool. Which will mean 24 separate hast resources, if I understand things correctly. -- Freddie Cash fjwcash@gmail.com