From owner-freebsd-questions Wed Jan 12 19: 7:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 9BF0F14EF8 for ; Wed, 12 Jan 2000 19:07:18 -0800 (PST) (envelope-from tbarnett@stdio.com) Received: (from tbarnett@localhost) by heathers.stdio.com (8.9.3/8.8.8) id WAA78568 for freebsd-questions@FreeBSD.ORG; Wed, 12 Jan 2000 22:07:09 -0500 (EST) (envelope-from tbarnett) Date: Wed, 12 Jan 2000 22:07:09 -0500 (EST) From: Tyler Barnett Message-Id: <200001130307.WAA78568@heathers.stdio.com> To: freebsd-questions@FreeBSD.ORG Subject: CCD recovery questions Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.3 stable, and created a 12GB CCD mirror from 2 identical disk drives. To test the scenario of one of them failing, I shutdown the system and unplugged one. During boot the ccd driver refused to config it. The system dropped into single-user mode for an fsck. I tried removing the "unplugged" disk drive from the ccd.conf line, effectively meaning that ccd0 had only 1 disk drive (the working one). It didn't work, still wanted to fsck. Of course, plugging the drive back in with the original ccd.conf, all works ok. I still haven't brought myself to test the scenario of unplugging a drive "hot", and seeing what happens :-) I'm not getting a warm fuzzy feeling about this. Unless I can figure out how to separate the ccd mirror, or run on 1 drive alone for a short period of time, I think I just statistically have halved the MTBF of either drive. And recovery from a drive failure as such seems impossible. BTW, I've used Solstice on Solaris (please no flames) and it has saved my bacon on a mirror failure. Otherwise, the FBSD ccd works just fine. I just want to know what to do when it doesn't. Anybody been there, done that? Thanks, Tyler Barnett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message