Date: Tue, 4 Apr 2000 16:26:09 -0400 (EDT) From: Mike Wade <mwade@cdc.net> To: "Jeffrey S. Sharp" <jss@subatomix.com> Cc: freebsd-small <freebsd-small@FreeBSD.ORG> Subject: Re: Mounting and Corruption Rehashed Message-ID: <Pine.GSO.4.10.10004041623150.22626-100000@server2> In-Reply-To: <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10004041623150.22626-100000>