From owner-freebsd-fs@FreeBSD.ORG Mon Dec 8 00:15:41 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C91306E6 for ; Mon, 8 Dec 2014 00:15:41 +0000 (UTC) Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AF9D8CE for ; Mon, 8 Dec 2014 00:15:40 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id bm13so2695937qab.40 for ; Sun, 07 Dec 2014 16:15:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=a3NtsijX/HstRUjzUCYwDFFHgmCG20yHEY8+WjXE43o=; b=B3EchRYzZxUNaZB5U+VXyf6ez4WwZH7r/VPgH+Ha2oj0xvCFwdrJjoUeDL9vy8bx5+ nqiYMex9FkmU9N2xfh3QmCWAQfKNJIawN1C9QNkUYz9vWgG3LsItsyMSruHQCaVnntk6 vi4KdFCGACpwO+Vl8xZTjgUI0n/oD4dWYvGNYtaRRjeqxnrrGirdwop4FBYk/+880zWf 2QF8JYp1x5vfSH+W0n5e5T6qVbxGnsyOUQqy3TvhCdOYb/3CsRc1s3pCMIGO4YoYfLSh jHV0wC7L1bPZAz7OLgbtoBX2phlCNw5KkbplIR9GRRJHclqSxoXrNXDKfVYsnrJu3CZO 5LXg== X-Gm-Message-State: ALoCoQlYRyor44/kri3Fjh+CZHppayh3eLuHj/JSYtE0Jqd5fmj5E3hGBoE9n3wGERbKHdWNusD2 MIME-Version: 1.0 X-Received: by 10.229.97.73 with SMTP id k9mr47425475qcn.15.1417997734510; Sun, 07 Dec 2014 16:15:34 -0800 (PST) Received: by 10.140.39.48 with HTTP; Sun, 7 Dec 2014 16:15:34 -0800 (PST) In-Reply-To: <5484D307.7070707@sorbs.net> References: <54825E70.20900@sorbs.net> <54842CC5.2020604@sorbs.net> <5484D307.7070707@sorbs.net> Date: Sun, 7 Dec 2014 17:15:34 -0700 Message-ID: Subject: Re: ZFS weird issue... From: Will Andrews To: Michelle Sullivan Content-Type: text/plain; charset=UTF-8 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 00:15:41 -0000 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. > The problem seems to be the guid -> device name transaltion is working > and failing because there is already a mfid8... and the re-number didn't > happen when the device was replaced... The guid -> device name translation isn't meant to be definitive at all times. It is just a cached mapping that can become out of date any time devices disappear and reappear or the system reboots. This is why ZFS uses the vdev GUIDs to determine which device is which regardless of what its current block device name is. --Will.