Date: Tue, 4 Apr 2000 15:30:27 -0500 From: "Jeffrey S. Sharp" <jss@subatomix.com> To: "Warner Losh" <imp@village.org> Cc: "freebsd-small" <freebsd-small@FreeBSD.ORG> Subject: Re: Mounting and Corruption Rehashed Message-ID: <005a01bf9e74$9d2bc6b0$2aa85c0a@vulcan> References: <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan> <200004041836.MAA70239@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> : The problem was this little paragraph from `man mount`: > : > : > Switching a filesystem back and forth between asynchronous > : > and normal operation or between read/write and read/only > : > access using ``mount -u'' may gradually bring about severe > : > filesystem corruption. > : > : Someone spoke up and said that they had actually > : experienced this corruption. > > I've not seen corruption. However, I oly change one or > two files somewhat infrequently and tend to reboot often > when I'm changing the underlying filesystem. 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. > 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! =============================== 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005a01bf9e74$9d2bc6b0$2aa85c0a>