From owner-freebsd-small Tue Apr 4 14:27:50 2000 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D2D7E37B99D for ; Tue, 4 Apr 2000 14:27:45 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA93948; Tue, 4 Apr 2000 15:27:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA71322; Tue, 4 Apr 2000 15:26:58 -0600 (MDT) Message-Id: <200004042126.PAA71322@harmony.village.org> To: Mike Wade Subject: Re: Mounting and Corruption Rehashed Cc: freebsd-small In-reply-to: Your message of "Tue, 04 Apr 2000 17:07:07 EDT." References: Date: Tue, 04 Apr 2000 15:26:57 -0600 From: Warner Losh Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Mike Wade writes: : > We've had similar corruptions on DiskOnChip w/o the ro -> rw -> ro : > junk :-(. : : Interesting... Any idea if it was software or hardware related? Any : details? How are you protecting yourself from corruption? =) We don't know. There were some bad chips a while ago that has been corrected. We don't know if these chips were just bad, or if there was a software problem. As for what we're doing to protect ourselves... We're migrating to using a CF <-> IDE adapter that we're building ourselves. Even doing this, we have a cost advantage over DOC given that the DOC prices haven't been falling at the same rate as CF has. : be able to update the flash for configuration data. Currently I have a : separate partition on flash for RW... That's what we do too. We have two partitions to make sure that we can switch over to the other one if we wear out the first partition. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message