Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We had 2 failed drives in our ZFS raidz1 pool. One had been resilvered to a spare and another was just out. The pool was in degraded mode.

I replaced both drives and began the resilver on the non-spare drive. Without thinking, I forced a resilver on the one that was currently running on the spare. The pool is now reporting LOTS of data errors.

Is there any way to recover from this or am I totally screwed? I would think that since the spare is still available, we're still only down 1 drive and the data should technically all be there. Also, did I cause this or did I just uncover existing data corruption?

share|improve this question
What exactly did you do? You can't force ZFS to "resilver", it does it on it's own. – Chris S Sep 26 '12 at 18:27
Obligatory "RAID is not backup" comment. – David Schwartz Sep 26 '12 at 18:42
Chris: I did a zpool replace -f app-pool (disk ID) for both disks. – Derek Sep 26 '12 at 18:50
Yeah, you're screwed. Can I ask why you would have included the -f option? It's one of those things they shouldn't have included in the first place, and there's no valid reason to use it ever. – Chris S Sep 26 '12 at 19:03
I did it to the 1st disk because it HAD been part of another pool and it gave me an error. On the 2nd disk it was a mistake. – Derek Sep 26 '12 at 19:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.