Date: Tue, 4 Apr 2000 14:16:05 -0500 From: "Jeffrey S. Sharp" <jss@subatomix.com> To: "freebsd-small" <freebsd-small@freebsd.org> Subject: Mounting and Corruption Rehashed Message-ID: <001f01bf9e6a$3a0b3c00$2aa85c0a@vulcan>
next in thread | raw e-mail | index | archive | help
Let's set the way-back knob to a few months ago. We were discussing the viability of doing the following: * Mounting flash read-only on / * Mounting small MFS filesystems on /var and /tmp * Temporarily remounting / read-write to make changes 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. Please excuse me if the following is a dumb question: why even mount the flash _read-only_ in the first place? If /var and /tmp are on separate filesystems (MFS), what write operations are going to happen to the flash that mounting read-only would prevent? Thanks, as always, for any helpful information. =============================== 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?001f01bf9e6a$3a0b3c00$2aa85c0a>