Date: Wed, 23 Dec 2009 17:04:30 -0800 From: Steven Schlansker <stevenschlansker@gmail.com> To: Rich <rincebrain@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Can't repair raidz2 (Cannot replace a replacing device) Message-ID: <DF83AA7B-8D1C-4448-A48B-DACC3A11D88D@gmail.com> In-Reply-To: <5da0588e0912231702v3e72e121j75ac077831723a15@mail.gmail.com> References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> <4B315320.5050504@quip.cz> <5da0588e0912221741r48395defnd11e34728d2b7b97@mail.gmail.com> <9CEE3EE5-2CF7-440E-B5F4-D2BD796EA55C@gmail.com> <5da0588e0912231644w2a7afb9dg41ceffbafc8c2df6@mail.gmail.com> <409922ED-42D5-4892-B74D-D2E696846AFB@gmail.com> <5da0588e0912231702v3e72e121j75ac077831723a15@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 23, 2009, at 5:02 PM, Rich wrote: > I mean, the report in that link I sent you was A) mine and B) on 13TB > of data I couldn't lose, so I can sympathize with the problem... > > A dirty solution might be to see if Solaris does the right thing with > ejecting the bad drive. That's not a bad plan. I've got a Solaris USB stick to boot off of, but it'll be a few days at least before I am within USB range of the server... :-p I do wish commodity hardware had remote reset functionality! Having a server crash remotely is so frustrating...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DF83AA7B-8D1C-4448-A48B-DACC3A11D88D>