From owner-freebsd-small Tue Apr 4 13:49:13 2000 Delivered-To: freebsd-small@freebsd.org Received: from cdc.net (server1.cdc.net [207.244.0.12]) by hub.freebsd.org (Postfix) with SMTP id E14B637BBF2 for ; Tue, 4 Apr 2000 13:49:05 -0700 (PDT) (envelope-from mwade@cdc.net) Received: (qmail 17488 invoked from network); 4 Apr 2000 20:26:09 -0000 Received: from unknown (HELO cdc.net) (207.244.0.13) by server1.cdc.net with SMTP; 4 Apr 2000 20:26:09 -0000 Received: (qmail 23337 invoked by uid 100); 4 Apr 2000 20:26:09 -0000 Date: Tue, 4 Apr 2000 16:26:09 -0400 (EDT) From: Mike Wade X-Sender: mwade@server2 To: "Jeffrey S. Sharp" Cc: freebsd-small Subject: Re: Mounting and Corruption Rehashed In-Reply-To: <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> 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 On Tue, 4 Apr 2000, Jeffrey S. Sharp wrote: > Good. I don't need to change stuff much or often in my application, > either. However, as soon as I get something booted using flash as root, > I'll do some testing to see if heavy writes + repeated remounting does > indeed cause corruption in a DiskOnChip. I've experienced file system corruption with the DiskOnChip while toggling back and forth between mount ro -> rw -> ro. All of my file data was mysteriously replaced with NULL's. Please let me know your findings though. =) > > The superblock gets updated from time to time. > > Aye, there's the rub! > > > Also, when things are mounted r/o you can power off at any > > time and know that the filesystem will be stable when you > > come back. > > Aye, there's the other rub! From my understanding a journaling filesystem would help out but does not exist yet on FreeBSD. Would the soft updates feature help any with preventing corruption due to reboots? --- Mike Wade (mwade@cdc.net) Director of Systems Administration CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message