ZFS: "Cannot replace a replacing drive"

Freddie Cash fjwcash at gmail.com
Fri Apr 30 21:01:35 UTC 2010


On Fri, Apr 30, 2010 at 1:59 PM, Wes Morgan <morganw at chemikals.org> wrote:

> On Fri, 30 Apr 2010, Wes Morgan wrote:
>
> > On Thu, 29 Apr 2010, Freddie Cash wrote:
> >
> > > On Thu, Apr 29, 2010 at 6:06 PM, Wes Morgan <morganw at chemikals.org>
> wrote:
> > >
> > > > On Wed, 28 Apr 2010, Freddie Cash wrote:
> > > >
> > > > > Going through the archives, I see that others have run into this
> issue,
> > > > and
> > > > > managed to solve it via "zpool detach".  However, looking closely
> at the
> > > > > archived messages, all the successful tests had one thing in
> common:  1
> > > > > drive ONLINE, 1 drive FAULTED.  If a drive is online, obviously it
> can be
> > > > > detached.  In all the cases where people have been unsuccessful at
> fixing
> > > > > this situation, 1 drive is OFFLINE, and 1 drive is FAULTED.  As is
> our
> > > > case:
> > > > >
> > > >
> > > > What happened to the drive to fault it?
> > > >
> > > > Am in the process of replacing 500 GB drives with 1.5 TB drives, to
> > > increase the available storage space in the pool (process went
> flawlessly on
> > > the other storage server).  First 3 disks in the vdev replaced without
> > > issues.
>
> Also, where is the original 500gb drive (#4) that you replaced? You should
> be able to put that drive back in and let it resilver itself to catch back
> up to the other devices, then cancel the replacement.
>

Oooh, never thought of trying that.  Makes sense.  I'll see if I can do that
this weekend.

-- 
Freddie Cash
fjwcash at gmail.com


More information about the freebsd-fs mailing list