Date: Fri, 30 Apr 2010 15:59:58 -0500 (CDT) From: Wes Morgan <morganw@chemikals.org> To: Freddie Cash <fjwcash@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: "Cannot replace a replacing drive" Message-ID: <alpine.BSF.2.00.1004301558010.32311@ibyngvyr> In-Reply-To: <alpine.BSF.2.00.1004301550160.32311@ibyngvyr> References: <y2pb269bc571004280847od80c334cmc3a073cd7d20a927@mail.gmail.com> <alpine.BSF.2.00.1004292005410.58938@ibyngvyr> <p2ib269bc571004291840m85acbbafna617db0825766fd3@mail.gmail.com> <alpine.BSF.2.00.1004301550160.32311@ibyngvyr>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1004301558010.32311>