Date: Sun, 10 Jun 2007 23:11:21 -0400 From: Francisco Reyes <lists@stringsutils.com> To: FreeBSD Filesystem <freebsd-fs@freebsd.org> Subject: Inode density for database machines - newfs -i Message-ID: <cone.1181531481.451392.13436.1000@zoraida.natserv.net>
next in thread | raw e-mail | index | archive | help
For my mailstore machines I usually do "newfs -i 32768" to decrease fsck time in case of problems. For database machines, postgresql in particular, would it help to have a number larger than 65536? I am aware that ZFS and gjournal are in the horizon, but I am looking at the next 3 months and neither of those two may be mature enough to even get approval to install them. Looking at one of my existing database machines, I have a filesystem using 1.2TB and only 2053 inodes. There are 3,539,385 free inodes. If I recall correctly I used "newfs -i 65536" for that filesystem. Will fsck be significantly faster in case of crash if I used say 131072(128K) or even 256K? What is the best list to find the current status of gjournal? This list of geom? Looking at archives most of the gjournal posts seem to be in current.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cone.1181531481.451392.13436.1000>