Date: Sun, 6 May 2001 18:30:51 -0500 From: Mike Meyer <mwm@mired.org> To: Jan Conrad <conrad@th.physik.uni-bonn.de> Cc: questions@freebsd.org Subject: Re: newfs options Message-ID: <15093.57003.451981.108064@guru.mired.org> In-Reply-To: <60672368@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Jan Conrad <conrad@th.physik.uni-bonn.de> types: > Hi, > > I would like to ask whether there is any need to choose newfs options > different from -b 8192 -f 1024 for larger partitions? > > For example, one of our partitions for homedirs (30GB) has an average file > size of 50kB. I guess it's just happy with the defaults. > > However, we have a partition (again 30GB) with an average file size of 5 MB! > What about that? > > any hints Yeah. You probably don't want to change the block size. Raising the block sizes raise the maximum file system and file sizes. Unless you're running into those, you don't need to raise it, and your file systems aren't anywhere near that size. The fragment size is limited by the block size. You can expect an average of 1/2 the fragment size of unused space per file. Raising the fragment size is probably a bad thing. Finally, raising the block size changes the behavior of the I/O system. If you know the files on the file system are going to be read in large contiguous chunks, you might want to raise the block size. Or you might want to raise maxcontig instead. The other thing to look at if you've got a lot of large files is changing the number of bytes per inode. By default, the system allocates a *lot* of inodes. You can lower that value if you know you won't need a lot of them. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15093.57003.451981.108064>