Date: Sat, 8 Dec 2001 19:08:14 +0100 From: Bernd Walter <ticso@cicely8.cicely.de> To: Marko Zec <zec@tel.fer.hr> Cc: "Louis A. Mamakos" <louie@TransSys.COM>, freebsd-arch@FreeBSD.ORG Subject: Re: Using a larger block size on large filesystems Message-ID: <20011208190814.A5998@cicely8.cicely.de> In-Reply-To: <3C1156B1.F44F844B@tel.fer.hr> References: <31807.1007732134@axl.seasidesoftware.co.za> <200112072257.fB7MvjE95211@apollo.backplane.com> <200112072311.fB7NB2723789@whizzo.transsys.com> <3C114FDF.138E09A7@tel.fer.hr> <200112072331.fB7NVM724075@whizzo.transsys.com> <3C1156B1.F44F844B@tel.fer.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 08, 2001 at 12:54:25AM +0100, Marko Zec wrote: > My point is if we all get used to seeing huge amounts of free space in /, then > we'll all be tempted to fill it up sooner or later with necessary or unnecessary > stuff. And then we can go into another cycle of / size expansion, and so on. Right > now my 4.4-R / uses 30M of space with a spare kernel image included, and I am not > feeling comfortable seeing it enlarged by an order of magnitude in the next > release. Those guys doing heavy development and needing multiple kernel/module > trees will anyhow make a custom partitioning, and for all other people a compact > sized / should be enough. Of course with /tmp extracted :) This is a / fs on a -current: ticso@cicely5# df -k / Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 38991 31022 4850 86% / And it's not /boot that filling it as I massivly reduced the contents: ticso@cicely5# du -k /boot 2684 /boot/kernel 12 /boot/defaults 1 /boot/modules 2241 /boot/kernel.work 5338 /boot A typical filled kernel directory is about 10-12M. Space is needed in /bin and /sbin: ticso@cicely5# du -k /bin /sbin 6224 /bin 16484 /sbin And /sbin is also reduced in my system. It's 40M sized because back in 2.2.x days it was absolutely more than enough. In todays situation I see 200M to be a good future size. Maybe we should tunefs to leave only a small amount space free to use. That way people get a clear sign not to fill it up. I'am still dreaming of a /boot partition and a volumegroup handling for everything else using vinum via sysinstall. Adding volumegroups to vinum isn't a difficult task as it's only a new labeltype. What needs to be done is that sysinstall knows the filling space for each directory and can help the user in his decision. Those who ever run the HP-UX installer will know what I mean. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011208190814.A5998>