From owner-freebsd-current Mon Jun 9 23:14:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA12566 for current-outgoing; Mon, 9 Jun 1997 23:14:52 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA12558 for ; Mon, 9 Jun 1997 23:14:49 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA10346; Mon, 9 Jun 1997 23:13:23 -0700 (PDT) To: "Michael L. VanLoon -- HeadCandy.com" cc: asami@cs.berkeley.edu (Satoshi Asami), burton@bsampley.vip.best.com, current@FreeBSD.ORG Subject: Re: overclocking In-reply-to: Your message of "Mon, 09 Jun 1997 21:58:38 PDT." <199706100458.VAA14947@MindBender.serv.net> Date: Mon, 09 Jun 1997 23:13:23 -0700 Message-ID: <10342.865923203@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm surprised, especially after Jordan's recent conversion to this > religion, trumpets blaring loudly and all. > > Trust me. Stripe your drives. It's worth it. Well, Jordan still has his questions about this new religion - my faith is not entirely pure. :-) Most importantly, I'd like to be able to migrate off and dismount a drive from a ccd or add one dynamically, automagically resizing the filesystem on it in either case, before I could ever consider it close to mission critical safe. As it stands now, you simply decrease your file system's fault-tolerance by a factor of the number of drives you have, and that sucks. I've already lost the ccd fs at current.freebsd.org once due to a drive crash, and it sure would be nice indeed to be able to: a) tell ccd to stop using a drive, b) tell ccd to migrate from a drive, if enough free space on other drives exists, and c) adopt a new drive. It still wouldn't stop CCD from being an AID rather than a RAID solution, but it sure would make the admin's life a hell of a lot easier in times of failure. Jordan