Date: Sat, 31 Dec 2011 19:08:18 -0500 From: Joshua Boyd <boydjd@jbip.net> To: Michael DeMan <freebsd@deman.com> Cc: freebsd-fs@freebsd.org Subject: Re: zfs detach/replace Message-ID: <CAHcKe7kXGFcuMJTL3UxMgfeBZ1vsVJOq8sBc0H76BLP_fUmQkQ@mail.gmail.com> In-Reply-To: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 31, 2011 at 1:58 AM, Michael DeMan <freebsd@deman.com> wrote: > Hi All, > > The origination of the problem is entirely my fault on FreeBSD 8.1 > RELEASE #0. We had old notes that attempting a 'replace' (which is > appropriate for a mirror) leaves ZFS in a funky state on BSD. I > inadvertently did just that on a drive swap on a raidz2 pool. My old notes > show the only recovery that we knew of at the time was to rsync or zfs-send > the pool elsewhere, destroy the local and rebuild from scratch. > I've never had a problem before, and have replaced about 5 drives in my striped raidz ... Usually I'll execute a zpool offline, camcontrol stop, remove the drive, then zpool replace. I am running 8-STABLE though, and not -RELEASE. -- Joshua Boyd E-mail: boydjd@jbip.net http://www.jbip.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHcKe7kXGFcuMJTL3UxMgfeBZ1vsVJOq8sBc0H76BLP_fUmQkQ>