From owner-freebsd-small Sat Apr 8 14:41:45 2000 Delivered-To: freebsd-small@freebsd.org Received: from lepton.subatomix.com (okc-224-168.mmcable.com [24.94.224.168]) by hub.freebsd.org (Postfix) with ESMTP id 012FE37B59C for ; Sat, 8 Apr 2000 14:41:43 -0700 (PDT) (envelope-from jss@lepton.subatomix.com) Received: from localhost (jss@localhost) by lepton.subatomix.com (8.9.3/8.9.3) with ESMTP id QAA39460 for ; Sat, 8 Apr 2000 16:43:46 -0500 (CDT) (envelope-from jss@lepton.subatomix.com) Date: Sat, 8 Apr 2000 16:43:46 -0500 (CDT) From: "Jeffrey S. Sharp" To: freebsd-small Subject: Corruption: My Initial Tests Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All right, here's some harder evidence. I ran something close to the following on a 3.4-RELEASE system for about 30 minutes against an 8MB DOC2K with a few files on it: #/bin/sh -x while ls; do mount -u -o rw /dev/fla0s1a /mnt cp testfile /mnt mount -u -o ro /dev/fla0s1a /mnt cat /mnt/testfile done When I stopped it, there was no corruption, and fsck reported no problems. 'Course, I didn't run it for days or transfer 6MB files. IMHO, however, I think the corruption Mike experienced was not caused by the mounting thing but was just a firmware/hardware problem. At any rate, we should be putting as much corruption detection/protection as possible into our flash-based applications if they do *any* writing to the flash, as the flash *will* eventually wear out. My apologies if I've beaten this dead penguin...er...horse too much. =============================== Jeffrey S. Sharp (XorAxAx) jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message