Date: Thu, 01 Jun 2006 01:04:00 -0400 From: Jonathan Noack <noackjr@alumni.rice.edu> To: Giorgos Keramidas <keramida@freebsd.org> Cc: freebsd-current@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: md /tmp and async mounts Message-ID: <447E7540.8070904@alumni.rice.edu> In-Reply-To: <20060601002024.GA1453@gothmog.pc> References: <20060522211223.GA3621@xor.obsecurity.org> <20060522231437.GC1446@odin.ac.hmc.edu> <20060523133037.GA2908@gothmog.pc> <20060523143013.GA11472@ci0.org> <20060523194106.GA46634@xor.obsecurity.org> <20060524203645.GB13500@gothmog.pc> <20060524203747.GA88742@xor.obsecurity.org> <20060524204617.GA13701@gothmog.pc> <20060601002024.GA1453@gothmog.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5FF8FB766EAF604A0C0A2A8A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 05/31/06 20:20, Giorgos Keramidas wrote: > The following diff should be sufficient for enabling -o async for > the MFS /tmp and MFS /var filesystems we support in our current > rc.d stuff: >=20 > %%% > Index: share/man/man5/rc.conf.5 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- share/man/man5/rc.conf.5 (revision 99) > +++ share/man/man5/rc.conf.5 (revision 101) > @@ -24,7 +24,7 @@ > .\" > .\" $FreeBSD: src/share/man/man5/rc.conf.5,v 1.298 2006/05/30 16:20:48= matteo Exp $ > .\" > -.Dd May 29, 2006 > +.Dd Jun 1, 2006 > .Dt RC.CONF 5 > .Os > .Sh NAME > @@ -241,12 +241,13 @@ > .Pa /tmp > is created. > The default is > -.Dq Li "-S -M" , > +.Dq Li "-S -M -o async" , > which inhibits the use of softupdates on > .Pa /tmp > to waste as little space as possible > -and creates a pure memory backed disk, which will never be swapped out= , > -for maximum performance and system stability at low memory conditions.= > +and creates a pure memory-backed disk, which uses asynchronous I/O > +and will never be swapped out, for maximum performance and system > +stability at low memory conditions. Given recent posts about panics with malloc-backed mds under low-memory conditions (see the "kmem leak in tmpmfs?" thread on stable@), I'm not sure keeping '-M' as the default for tmpmfs and varmfs is advisable. Here is the rather ominous note on using malloc-backed mds in mdconfig(8)= : "Storage for this type of memory disk is allocated with malloc(9). This limits the size to the malloc bucket limit in the kernel. If the -o reserve option is not set, creating and filling a large malloc-backed memory disk is a very easy way to panic a system." -Jonathan --=20 Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195 --------------enig5FF8FB766EAF604A0C0A2A8A 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.4.3 (FreeBSD) iD8DBQFEfnVGUFz01pkdgZURAtF2AJ4mgpr5APUyucPcL6u8fhV7WtNBQwCfUE4R l75fgA4EQgWw587nAs0noTA= =+Kr1 -----END PGP SIGNATURE----- --------------enig5FF8FB766EAF604A0C0A2A8A--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?447E7540.8070904>