Date: Sun, 7 Dec 2014 17:15:34 -0700 From: Will Andrews <will@firepipe.net> To: Michelle Sullivan <michelle@sorbs.net> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: ZFS weird issue... Message-ID: <CADBaqmiJyiYrVhU5NKG1C2N=BGYbZ97%2BYO14btaviGuYGstPmw@mail.gmail.com> In-Reply-To: <5484D307.7070707@sorbs.net> References: <54825E70.20900@sorbs.net> <CADBaqmiPM7nSASjc80HpS1%2Bk62DwBnrr5DbwHQtWHyr7%2BwCE8A@mail.gmail.com> <54842CC5.2020604@sorbs.net> <CADBaqminLE%2BN1x9SYpuwf1LM9t7xQ8H=pj9RQW1vdECEThMH-A@mail.gmail.com> <5484D307.7070707@sorbs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 7, 2014 at 3:21 PM, Michelle Sullivan <michelle@sorbs.net> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADBaqmiJyiYrVhU5NKG1C2N=BGYbZ97%2BYO14btaviGuYGstPmw>