From owner-freebsd-arch Sat Dec 8 10:13: 1 2001 Delivered-To: freebsd-arch@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id A6AE937B405 for ; Sat, 8 Dec 2001 10:12:54 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.0/8.11.0) with UUCP id fB8ICb663397; Sat, 8 Dec 2001 19:12:37 +0100 (CET) Received: from mail.cicely.de (cicely20.cicely.de [10.1.1.22]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id fB8I8Gtx055717; Sat, 8 Dec 2001 19:08:17 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0/8.11.0) with ESMTP id fB8I8GW01934; Sat, 8 Dec 2001 19:08:16 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id fB8I8F006143; Sat, 8 Dec 2001 19:08:15 +0100 (CET) (envelope-from ticso) Date: Sat, 8 Dec 2001 19:08:14 +0100 From: Bernd Walter To: Marko Zec Cc: "Louis A. Mamakos" , freebsd-arch@FreeBSD.ORG Subject: Re: Using a larger block size on large filesystems Message-ID: <20011208190814.A5998@cicely8.cicely.de> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1156B1.F44F844B@tel.fer.hr> User-Agent: Mutt/1.3.23i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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