From owner-freebsd-fs@FreeBSD.ORG Thu May 19 23:28:07 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 BF1E31065673; Thu, 19 May 2011 23:28:07 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1F6748FC24; Thu, 19 May 2011 23:28:07 +0000 (UTC) Received: by yie12 with SMTP id 12so1426295yie.13 for ; Thu, 19 May 2011 16:28:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ym8u8IGtfSN/rRKs6yU+hYsBIJeYFC6VGW1jWFWxQu0=; b=uKWjgXfFLCWGiek7IZHTk9TYnrr0j5vbLWGJrn45yAzMqkuFkuA45q1euPaQzJKdwK CyuMHtX+pV8Ly7G6mDHR1a54sTH6HqoKOT01qwGSrWG7CbUObxJ7nnGQK6OLEzqia3IF wafelRF/sylFZtgTEvQKy3sUTynJmuCaDR1KQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ox9r4SnS2COjOVXzPfC8EyqmNFqYaE5qZlYCT+GxuuKe33U0dntH0GP0+0NhzkyoCw CMapFNcm708yq3aSBHN93rwthMMLQ1eBmd52NItcrYhhvUijY/dK4z4lNRDqkH9903t/ Yss1tOzoHgda7OFiq3vnG/AB8vaQMqzDJAZdI= MIME-Version: 1.0 Received: by 10.90.147.18 with SMTP id u18mr257479agd.95.1305847686607; Thu, 19 May 2011 16:28:06 -0700 (PDT) Received: by 10.90.138.17 with HTTP; Thu, 19 May 2011 16:28:06 -0700 (PDT) In-Reply-To: <20110519232551.GG2100@garage.freebsd.pl> References: <85EC77D3-116E-43B0-BFF1-AE1BD71B5CE9@itassistans.se> <20110519181436.GB2100@garage.freebsd.pl> <4DD5A1CF.70807@itassistans.se> <20110519230921.GF2100@garage.freebsd.pl> <20110519232551.GG2100@garage.freebsd.pl> Date: Thu, 19 May 2011 16:28:06 -0700 Message-ID: From: Freddie Cash To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: HAST + ZFS self healing? Hot spares? 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: Thu, 19 May 2011 23:28:07 -0000 On Thu, May 19, 2011 at 4:25 PM, Pawel Jakub Dawidek wrote: > On Thu, May 19, 2011 at 04:22:57PM -0700, Freddie Cash wrote: > > With HAST, there's only a couple of small changes needed: > > - zpool offline poolname diskname <-- removes the /dev/hast node > > from the pool > > - hastctl role init diskname <-- removes the /dev/hast node > > - remove dead disk > > - insert new disk > > - partition, label, etc as needed > > - hastctl role create diskname <-- creates the hast resource > > - hastctl role primary diskname <-- creates the new /dev/hast > node > > - zpool replace poolname olddisk newdisk <-- adds the /dev/hast node to > > pool > > - wait for resilver to complete > > > > The downside to this setup is that the data on the disk in the secondary > > node is lost, as the resilver of the disk on the primary node recreates > all > > the data on the secondary node. But, at least then you know the data is > > good on both disks in the HAST resource. > > It shouldn't be the case. Primary HAST node should synchronize data from > secondary HAST node, as primary has new disk. This should allow you to > simply 'zpool online poolname disk' instead of replacing it. > It doesn't work that way for you? > Oh? Never thought to try that. But, I guess that does make sense ... and is the point of having the redundant data in the other server ... Also, in my tests, I was running a degraded HAST setup (only 1 server), so it wouldn't have been possible to do. Will have to remember that for the next time I'm playing with HAST (the box is currently a non-HAST setup). -- Freddie Cash fjwcash@gmail.com