From owner-freebsd-stable@FreeBSD.ORG Mon Jul 19 16:18:27 2010 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 1052F106567A for ; Mon, 19 Jul 2010 16:18:27 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id BBA498FC17 for ; Mon, 19 Jul 2010 16:18:26 +0000 (UTC) Received: by gxk24 with SMTP id 24so2769067gxk.13 for ; Mon, 19 Jul 2010 09:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=WPjcoXShfHDD7+sPyTF7G+nbJRrjiyuVAepjZBsZq1w=; b=TEsMaI8OvcsO6Mg7s3/esB5D7YnE/P/FEmXy7xBkuuhHExcFrj0mAsisFW3Y1+oGsL 9q0IcYveAKM6wziPkgHLBW+vSYVnRf7f3a2jI8kfyIkZBhSBg83CMxaRKVJJBg9GHqZ8 Bdb0P2tFnwuLTkirKYkDqE8KpkFsRl91W1n10= 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=Yua32NCAyETjQF8QSwIpHeaXBW11bN8N/gLiG/9f9kfZ8ZRNWtc7Gnm+4oLhKfYifv qTPR7kGM3Px6+xa1pwqoJoZgfcbZM/aes8N8Zc6XNYxr+1iyejof9nBaGsWR6FAcMJTs Zw+6hAJZ2jYbJrWY2suiba/S2vzRio4IABLr8= MIME-Version: 1.0 Received: by 10.224.80.69 with SMTP id s5mr4423730qak.5.1279556305670; Mon, 19 Jul 2010 09:18:25 -0700 (PDT) Received: by 10.229.29.71 with HTTP; Mon, 19 Jul 2010 09:18:25 -0700 (PDT) In-Reply-To: References: Date: Mon, 19 Jul 2010 11:18:25 -0500 Message-ID: From: Adam Vande More To: Garrett Moore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable Subject: Re: Problems replacing failing drive in ZFS pool 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: Mon, 19 Jul 2010 16:18:27 -0000 On Mon, Jul 19, 2010 at 10:56 AM, Garrett Moore wrote: > So you think it's because when I switch from the old disk to the new disk, > ZFS doesn't realize the disk has changed, and thinks the data is just > corrupt now? Even if that happens, shouldn't the pool still be available, > since it's RAIDZ1 and only one disk has gone away? > > I don't have / on ZFS; I'm only using it as a 'data' partition, so I should > be able to try your suggestion. My only concern: is there any risk of > trashing my pool if I try your instructions? Everything I've done so far, > even when told "insufficient replicas / corrupt data", has not cost me any > data as long as I switch back to the original (dying) drive. If I mix in > export/import statements which might 'touch' the pool, is there a chance it > will choke and trash my data? > I'm not sure what's going on in your case, but I have cron'd a zpool scrub for my pool on weekly basis to avoid this. I run a / zfs mirror and one day I could no longer boot and saw the dread 'insufficient replicas'. I eventually got it when disk started to work again briefly then did a snapshot/send offsite, redid system with new install & disk then restored data. The export/import shouldn't hurt, I used that when booting off an MFSBSD cd and imported the zpool to send from there. Perhaps you might want to consider RAIDZ2 with all those disks. -- Adam Vande More