Date: Wed, 19 Nov 1997 12:30:39 -0800 From: Aaron Smith <aaron@veritas.com> To: hackers@freebsd.org Subject: MFS /tmp oddness Message-ID: <m0xYGlp-0000CuC@megami.veritas.com>
next in thread | raw e-mail | index | archive | help
i'm having this problem where a boot-time-mounted MFS ends up being sized to 32M. if i unmount and remount it, it's 128M. thinking that DFLDSIZ was the problem, i upped MAX and DFLDSIZ to 256M, but no dice. does anybody know why i'm getting such a tiny MFS? we tried using the -s option too but that didn't work either. sorry if this is a FAQ, i searched the mailing list archives to no avail. aaron On Mon, 17 Nov 1997 22:22:10 PST, John-Mark Gurney writes: >but be careful... normally you can only have a 64meg mfs unless you >increase the datasize limit to be larger than 64megs... I build my >kernel with: >options "MAXDSIZ=(512*1024*1024)" >options "DFLDSIZ=(512*1024*1024)" > >so that I can have: >Filesystem 1K-blocks Used Avail Capacity Mounted on >mfs:26 254319 62731 171243 27% /tmp > >note that the -s option specifies the size of the fs in 512byte blocks... >there is an option to have the mfs /tmp backed by a file (so if you >reboot your machine, your /tmp contents are saved, not sure if this >hurts performane or not) which helps prevents lose of data...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0xYGlp-0000CuC>