From owner-freebsd-hackers Fri Sep 28 16:45:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 1601237B408 for ; Fri, 28 Sep 2001 16:45:27 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f8SNjQE40283 for freebsd-hackers@freebsd.org; Fri, 28 Sep 2001 19:45:26 -0400 (EDT) (envelope-from bicknell) Date: Fri, 28 Sep 2001 19:45:26 -0400 From: Leo Bicknell To: freebsd-hackers@freebsd.org Subject: Mirrored / redundant disks. Message-ID: <20010928194526.A40019@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I need to configure a server that can deal with a disk failure. I've been looking at CCD and Vinum, but both seem to have issues that make automatic recovery in the face of one dead disk (in a mirror) less than optimal. So, if you know how to make it so a disk can die and the box keeps running, and more importantly _can be rebooted_ and keep running either via careful configuration or some crufty scripts if you could contact me that would be welcome. No need to keep on-list unless you think there's something of great value to hackers. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message