From owner-freebsd-fs@FreeBSD.ORG Mon Dec 8 06:15:57 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19395D51 for ; Mon, 8 Dec 2014 06:15:57 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 03A0DC9A for ; Mon, 8 Dec 2014 06:15:56 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NG900IB42Y0FI00@hades.sorbs.net> for freebsd-fs@freebsd.org; Sun, 07 Dec 2014 22:20:26 -0800 (PST) Message-id: <54854219.9040807@sorbs.net> Date: Mon, 08 Dec 2014 07:15:53 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Will Andrews Subject: Re: ZFS weird issue... References: <54825E70.20900@sorbs.net> <54842CC5.2020604@sorbs.net> <5484D307.7070707@sorbs.net> In-reply-to: Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 06:15:57 -0000 Will Andrews wrote: > On Sun, Dec 7, 2014 at 3:21 PM, Michelle Sullivan wrote: > >> root@colossus:~ # zpool replace sorbs spare-8 mfid8 >> root@colossus:~ # zpool replace sorbs spare-8 mfid15 >> root@colossus:~ # zpool replace sorbs 933862663 1702922605 >> root@colossus:~ # zpool replace sorbs mfid8 mfid8 >> root@colossus:~ # zpool replace sorbs mfid15 mfid15 >> root@colossus:~ # zpool replace sorbs spare-8 1702922605 >> root@colossus:~ # zpool replace sorbs 1702922605 spare-8 >> root@colossus:~ # zpool replace sorbs 1702922605 mfid8 >> > [...] > > I believe you want to replace 1702922605 (the original member that > used to be mfid8) with mfid15, not mfid8. According to your 'zpool > status' output (which I assume is still current?), mfid8 is now a > different member of the raidz2 than it was previously. Of the 16 > devices you have, only mfid15 is currently missing, which suggests > that it's the current name of the new drive. > > As you said, it's a brand new drive, so "zdb -l /dev/mfid15" should > confirm that it has no ZFS labels, and therefore is the correct drive > to use as the replacement for 1702922605. > > Thank you! (that seems to have got it) root@colossus:/ # zpool replace sorbs 1702922605 mfid15 root@colossus:/ # zpool status -v pool: VirtualDisks state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM VirtualDisks ONLINE 0 0 0 zvol/sorbs/VirtualDisks ONLINE 0 0 0 errors: No known data errors pool: sorbs state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Mon Dec 8 07:13:45 2014 21.6M scanned out of 29.9T at 1.14M/s, (scan is slow, no estimated time) 1.37M resilvered, 0.00% done config: NAME STATE READ WRITE CKSUM sorbs DEGRADED 0 0 0 raidz2-0 DEGRADED 0 0 0 mfid0 ONLINE 0 0 0 mfid1 ONLINE 0 0 0 mfid2 ONLINE 0 0 0 mfid3 ONLINE 0 0 0 mfid4 ONLINE 0 0 0 mfid5 ONLINE 0 0 0 mfid6 ONLINE 0 0 0 mfid7 ONLINE 0 0 0 spare-8 DEGRADED 0 0 0 replacing-0 UNAVAIL 0 0 0 1702922605 FAULTED 0 0 0 was /dev/mfid8 mfid15 ONLINE 0 0 0 (resilvering) mfid14 ONLINE 0 0 0 mfid8 ONLINE 0 0 0 mfid9 ONLINE 0 0 0 mfid10 ONLINE 0 0 0 mfid11 ONLINE 0 0 0 mfid12 ONLINE 0 0 0 mfid13 ONLINE 0 0 0 spares 933862663 INUSE was /dev/mfid14 errors: No known data errors root@colossus:/ # -- Michelle Sullivan http://www.mhix.org/