Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Dec 2007 01:47:25 +0100
From:      Ivan Voras <ivoras@freebsd.org>
To:        freebsd-doc@freebsd.org
Cc:        freebsd-current@freebsd.org
Subject:   Re: FreeBSD 7 trivial problems / notes
Message-ID:  <fji2b0$ki7$1@ger.gmane.org>
In-Reply-To: <20071210002131.GA74729@kobe.laptop>
References:  <fjho0k$hdc$1@ger.gmane.org> <20071209234943.GB2112@kobe.laptop>	<9bbcef730712091554p63d4ec54sdaf0abcb6e5b1c65@mail.gmail.com> <20071210002131.GA74729@kobe.laptop>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig499D342CBF81FAC5722DE578
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Giorgos Keramidas wrote:

> For example, does it make sense to fsck a tmpfs, ever?  When it's not
> mounted, is it accessible in any way?  What are the `use cases' of the
> tmpfs filesystem, other than memory-backed /tmp mounts?

fscking tmpfs, if it does make sense, can't ever be done from the
userland; fsck_tmpfs could, in theory, only instigate the kernel file
system driver to "do something" and probably return some sort of simple
status result - it would be much harder to do any kind of superuser
interaction like the "normal" fsck programs do.

While there could, in theory, be some kind of scrubbing function in the
kernel module that traverses the in-memory structures, I doubt it would
make sense - I suspect the system would crash very soon if a memory
corruption or a bug that mangles the structures existed. Possibly
defragmentation could be useful, but I don't know enough about tmpfs to
say for sure.



--------------enig499D342CBF81FAC5722DE578
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHXIydldnAQVacBcgRAnTiAJ4uKU+JNEs4dkRCBzCar4U1IlHrAwCfd6Cl
jmEkp+gCEfG91EtBWPE6E4o=
=ou7x
-----END PGP SIGNATURE-----

--------------enig499D342CBF81FAC5722DE578--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fji2b0$ki7$1>