From owner-freebsd-questions Fri Aug 4 17:22:18 2000 Delivered-To: freebsd-questions@freebsd.org Received: from relay.lppi.com (relay.lppi.com [208.49.169.66]) by hub.freebsd.org (Postfix) with ESMTP id 230CB37B7B8 for ; Fri, 4 Aug 2000 17:22:07 -0700 (PDT) (envelope-from lew@lppi.com) Date: Fri, 4 Aug 2000 17:22:06 -0700 (PDT) Message-Id: <200008050022.RAA14034@relay.lppi.com> From: Lew payne To: Andy Hogben Cc: freebsd-questions@freebsd.org Subject: Re: EIDE Problems - fsbn read error In-Reply-To: <200008050000.RAA26599@mirage.informix.com> References: <200008042340.QAA14005@relay.lppi.com> <200008050000.RAA26599@mirage.informix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.23 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In previous messages to the freebsd-questions list you've mentioned > that you simply have two drives in each machine and then use pax > every night to do your 'mirroring'. However, here you say: > > > One of our new FreeBSD 3.5-REL systems is periodically locking up, > > due to an apparent disk error. These are brand-new IBM 7200 RPM > > 60 GB ATA/66 EIDE drives, in a ccd configuration as follows: Apples and oranges. The two messages are unrelated. The fsbn error is happening on our news machine (we're the 57th largest distributor of usenet news in the world, per the Usenet Top 1000 report). I don't back up the news spool on that system, it is not critical (and too damn large). All my web servers have dual EIDE ATA/66 7200 RPM disks, and they are the ones I back up -- my bread and butter. I got tired of doing dumps to tape (via amanda), or of doing RDIST backups to another box. One of the boxes I back up via pax is ns1.lppi.com and mail1.lppi.com, just like what you're planning on doing. Two drives, set up on the same controller as master and slave. But make sure to install at least a skeleton FreeBSD on the slave, so you get it BOOTABLE !!! Or, you can boot off CD and do a "dd" from master to slave the 1st time to make sure you copy the boot block... though I think you won't be able to boot it unless you make the "slave" a "master" should the real "master" fail. Also, /etc/fstab will bite you. Hope that helps... --- Lew Payne Publishing, Inc. Dunn & Bradstreet listed 994 San Antonio Road DUNS # 055037852 Palo Alto, CA 94303 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message