1994-05-26 06:35:07 +00:00
|
|
|
/*
|
|
|
|
|
* Copyright (c) 1983, 1993
|
|
|
|
|
* The Regents of the University of California. All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
|
* are met:
|
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
|
|
|
* must display the following acknowledgement:
|
|
|
|
|
* This product includes software developed by the University of
|
|
|
|
|
* California, Berkeley and its contributors.
|
|
|
|
|
* 4. Neither the name of the University nor the names of its contributors
|
|
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
|
* without specific prior written permission.
|
|
|
|
|
*
|
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef lint
|
1998-08-03 06:41:20 +00:00
|
|
|
static const char copyright[] =
|
1994-05-26 06:35:07 +00:00
|
|
|
"@(#) Copyright (c) 1983, 1993\n\
|
|
|
|
|
The Regents of the University of California. All rights reserved.\n";
|
|
|
|
|
#endif /* not lint */
|
|
|
|
|
|
|
|
|
|
#ifndef lint
|
1998-08-03 06:41:20 +00:00
|
|
|
#if 0
|
1994-05-26 06:35:07 +00:00
|
|
|
static char sccsid[] = "@(#)tunefs.c 8.2 (Berkeley) 4/19/94";
|
1998-08-03 06:41:20 +00:00
|
|
|
#endif
|
|
|
|
|
static const char rcsid[] =
|
1999-08-28 00:22:10 +00:00
|
|
|
"$FreeBSD$";
|
1994-05-26 06:35:07 +00:00
|
|
|
#endif /* not lint */
|
|
|
|
|
|
|
|
|
|
/*
|
2002-08-21 18:11:48 +00:00
|
|
|
* tunefs: change layout parameters to an existing file system.
|
1994-05-26 06:35:07 +00:00
|
|
|
*/
|
|
|
|
|
#include <sys/param.h>
|
1999-01-20 01:22:39 +00:00
|
|
|
#include <sys/mount.h>
|
2002-05-12 21:37:08 +00:00
|
|
|
#include <sys/disklabel.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <sys/stat.h>
|
|
|
|
|
|
1999-01-20 01:22:39 +00:00
|
|
|
#include <ufs/ufs/ufsmount.h>
|
2002-06-21 06:18:05 +00:00
|
|
|
#include <ufs/ufs/dinode.h>
|
|
|
|
|
#include <ufs/ffs/fs.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
|
|
|
|
|
#include <err.h>
|
|
|
|
|
#include <fcntl.h>
|
|
|
|
|
#include <fstab.h>
|
2003-01-20 21:15:02 +00:00
|
|
|
#include <libufs.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <paths.h>
|
1998-08-03 06:41:20 +00:00
|
|
|
#include <stdio.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <stdlib.h>
|
2000-03-14 07:44:32 +00:00
|
|
|
#include <string.h>
|
1994-05-26 06:35:07 +00:00
|
|
|
#include <unistd.h>
|
|
|
|
|
|
|
|
|
|
/* the optimization warning string template */
|
|
|
|
|
#define OPTWARN "should optimize for %s with minfree %s %d%%"
|
|
|
|
|
|
2003-01-20 21:15:02 +00:00
|
|
|
struct uufsd disk;
|
|
|
|
|
#define sblock disk.d_fs
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2002-03-21 13:20:49 +00:00
|
|
|
void usage(void);
|
|
|
|
|
void printfs(void);
|
1994-05-26 06:35:07 +00:00
|
|
|
|
|
|
|
|
int
|
2003-01-20 21:15:02 +00:00
|
|
|
main(int argc, char *argv[])
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
2003-01-28 02:42:01 +00:00
|
|
|
const char *special, *on;
|
2001-07-15 05:47:47 +00:00
|
|
|
const char *name;
|
2002-10-14 19:52:12 +00:00
|
|
|
int Aflag = 0, active = 0, aflag = 0;
|
|
|
|
|
int eflag = 0, fflag = 0, lflag = 0, mflag = 0;
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
int nflag = 0, oflag = 0, pflag = 0, sflag = 0;
|
2002-09-06 07:59:10 +00:00
|
|
|
int evalue = 0, fvalue = 0;
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
int mvalue = 0, ovalue = 0, svalue = 0;
|
2002-10-14 19:52:12 +00:00
|
|
|
char *avalue = NULL, *lvalue = NULL, *nvalue = NULL;
|
2001-07-15 05:47:47 +00:00
|
|
|
const char *chg[2];
|
1999-01-20 01:22:39 +00:00
|
|
|
struct ufs_args args;
|
|
|
|
|
struct statfs stfs;
|
2000-11-28 18:17:15 +00:00
|
|
|
int found_arg, ch;
|
1994-05-26 06:35:07 +00:00
|
|
|
|
2000-11-28 18:17:15 +00:00
|
|
|
if (argc < 3)
|
|
|
|
|
usage();
|
|
|
|
|
found_arg = 0; /* at least one arg is required */
|
2002-10-15 15:30:55 +00:00
|
|
|
while ((ch = getopt(argc, argv, "Aa:e:f:l:m:n:o:ps:")) != -1)
|
2000-11-28 18:17:15 +00:00
|
|
|
switch (ch) {
|
2002-10-15 15:30:55 +00:00
|
|
|
case 'A':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
Aflag++;
|
|
|
|
|
break;
|
2002-10-14 19:52:12 +00:00
|
|
|
case 'a':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "ACLs";
|
|
|
|
|
avalue = optarg;
|
|
|
|
|
if (strcmp(avalue, "enable") && strcmp(avalue, "disable")) {
|
|
|
|
|
errx(10, "bad %s (options are %s)", name,
|
|
|
|
|
"`enable' or `disable'");
|
|
|
|
|
}
|
|
|
|
|
aflag = 1;
|
|
|
|
|
break;
|
2000-11-28 18:17:15 +00:00
|
|
|
case 'e':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "maximum blocks per file in a cylinder group";
|
2000-12-10 20:59:30 +00:00
|
|
|
evalue = atoi(optarg);
|
|
|
|
|
if (evalue < 1)
|
2000-11-28 18:17:15 +00:00
|
|
|
errx(10, "%s must be >= 1 (was %s)", name, optarg);
|
2000-12-10 20:59:30 +00:00
|
|
|
eflag = 1;
|
2000-11-28 18:17:15 +00:00
|
|
|
break;
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
case 'f':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "average file size";
|
|
|
|
|
fvalue = atoi(optarg);
|
|
|
|
|
if (fvalue < 1)
|
|
|
|
|
errx(10, "%s must be >= 1 (was %s)", name, optarg);
|
|
|
|
|
fflag = 1;
|
|
|
|
|
break;
|
2002-10-14 19:52:12 +00:00
|
|
|
case 'l':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "multilabel MAC file system";
|
|
|
|
|
lvalue = optarg;
|
|
|
|
|
if (strcmp(lvalue, "enable") && strcmp(lvalue, "disable")) {
|
|
|
|
|
errx(10, "bad %s (options are %s)", name,
|
|
|
|
|
"`enable' or `disable'");
|
|
|
|
|
}
|
|
|
|
|
lflag = 1;
|
|
|
|
|
break;
|
2000-11-28 18:17:15 +00:00
|
|
|
case 'm':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "minimum percentage of free space";
|
2000-12-10 20:59:30 +00:00
|
|
|
mvalue = atoi(optarg);
|
|
|
|
|
if (mvalue < 0 || mvalue > 99)
|
2000-11-28 18:17:15 +00:00
|
|
|
errx(10, "bad %s (%s)", name, optarg);
|
2000-12-10 20:59:30 +00:00
|
|
|
mflag = 1;
|
2000-11-28 18:17:15 +00:00
|
|
|
break;
|
|
|
|
|
case 'n':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "soft updates";
|
2000-12-10 20:59:30 +00:00
|
|
|
nvalue = optarg;
|
|
|
|
|
if (strcmp(nvalue, "enable") && strcmp(nvalue, "disable")) {
|
2000-11-28 18:17:15 +00:00
|
|
|
errx(10, "bad %s (options are %s)",
|
|
|
|
|
name, "`enable' or `disable'");
|
|
|
|
|
}
|
2000-12-10 20:59:30 +00:00
|
|
|
nflag = 1;
|
2000-11-28 18:17:15 +00:00
|
|
|
break;
|
|
|
|
|
case 'o':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "optimization preference";
|
|
|
|
|
chg[FS_OPTSPACE] = "space";
|
|
|
|
|
chg[FS_OPTTIME] = "time";
|
|
|
|
|
if (strcmp(optarg, chg[FS_OPTSPACE]) == 0)
|
2000-12-10 20:59:30 +00:00
|
|
|
ovalue = FS_OPTSPACE;
|
2000-11-28 18:17:15 +00:00
|
|
|
else if (strcmp(optarg, chg[FS_OPTTIME]) == 0)
|
2000-12-10 20:59:30 +00:00
|
|
|
ovalue = FS_OPTTIME;
|
2000-11-28 18:17:15 +00:00
|
|
|
else
|
|
|
|
|
errx(10, "bad %s (options are `space' or `time')",
|
1994-05-26 06:35:07 +00:00
|
|
|
name);
|
2000-12-10 20:59:30 +00:00
|
|
|
oflag = 1;
|
2000-11-28 18:17:15 +00:00
|
|
|
break;
|
|
|
|
|
case 'p':
|
2001-01-29 11:00:16 +00:00
|
|
|
found_arg = 1;
|
2000-12-10 20:59:30 +00:00
|
|
|
pflag = 1;
|
|
|
|
|
break;
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
case 's':
|
|
|
|
|
found_arg = 1;
|
|
|
|
|
name = "expected number of files per directory";
|
|
|
|
|
svalue = atoi(optarg);
|
|
|
|
|
if (svalue < 1)
|
|
|
|
|
errx(10, "%s must be >= 1 (was %s)", name, optarg);
|
|
|
|
|
sflag = 1;
|
|
|
|
|
break;
|
2000-11-28 18:17:15 +00:00
|
|
|
default:
|
1994-05-26 06:35:07 +00:00
|
|
|
usage();
|
2000-11-28 18:17:15 +00:00
|
|
|
}
|
|
|
|
|
argc -= optind;
|
|
|
|
|
argv += optind;
|
|
|
|
|
|
|
|
|
|
if (found_arg == 0 || argc != 1)
|
|
|
|
|
usage();
|
|
|
|
|
|
2003-01-28 02:42:01 +00:00
|
|
|
on = special = argv[0];
|
|
|
|
|
if (ufs_disk_fillout(&disk, special) == -1)
|
|
|
|
|
goto err;
|
|
|
|
|
if (disk.d_name != special) {
|
|
|
|
|
special = disk.d_name;
|
2000-12-10 20:59:30 +00:00
|
|
|
if (statfs(special, &stfs) == 0 &&
|
2003-01-28 02:42:01 +00:00
|
|
|
strcmp(special, stfs.f_mntonname) == 0)
|
2000-12-10 20:59:30 +00:00
|
|
|
active = 1;
|
2003-01-20 21:15:02 +00:00
|
|
|
}
|
2000-12-10 20:59:30 +00:00
|
|
|
|
|
|
|
|
if (pflag) {
|
|
|
|
|
printfs();
|
|
|
|
|
exit(0);
|
|
|
|
|
}
|
2002-10-14 19:52:12 +00:00
|
|
|
if (aflag) {
|
|
|
|
|
name = "ACLs";
|
|
|
|
|
if (strcmp(avalue, "enable") == 0) {
|
|
|
|
|
if (sblock.fs_flags & FS_ACLS) {
|
|
|
|
|
warnx("%s remains unchanged as enabled", name);
|
|
|
|
|
} else {
|
|
|
|
|
sblock.fs_flags |= FS_ACLS;
|
|
|
|
|
warnx("%s set", name);
|
|
|
|
|
}
|
|
|
|
|
} else if (strcmp(avalue, "disable") == 0) {
|
|
|
|
|
if ((~sblock.fs_flags & FS_ACLS) ==
|
|
|
|
|
FS_ACLS) {
|
|
|
|
|
warnx("%s remains unchanged as disabled",
|
|
|
|
|
name);
|
|
|
|
|
} else {
|
|
|
|
|
sblock.fs_flags &= ~FS_ACLS;
|
2002-10-16 05:03:40 +00:00
|
|
|
warnx("%s cleared", name);
|
2002-10-14 19:52:12 +00:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
2000-12-10 20:59:30 +00:00
|
|
|
if (eflag) {
|
|
|
|
|
name = "maximum blocks per file in a cylinder group";
|
|
|
|
|
if (sblock.fs_maxbpg == evalue) {
|
|
|
|
|
warnx("%s remains unchanged as %d", name, evalue);
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
warnx("%s changes from %d to %d",
|
|
|
|
|
name, sblock.fs_maxbpg, evalue);
|
|
|
|
|
sblock.fs_maxbpg = evalue;
|
|
|
|
|
}
|
|
|
|
|
}
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
if (fflag) {
|
|
|
|
|
name = "average file size";
|
|
|
|
|
if (sblock.fs_avgfilesize == fvalue) {
|
|
|
|
|
warnx("%s remains unchanged as %d", name, fvalue);
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
warnx("%s changes from %d to %d",
|
|
|
|
|
name, sblock.fs_avgfilesize, fvalue);
|
|
|
|
|
sblock.fs_avgfilesize = fvalue;
|
|
|
|
|
}
|
|
|
|
|
}
|
2002-10-14 19:52:12 +00:00
|
|
|
if (lflag) {
|
|
|
|
|
name = "multilabel";
|
|
|
|
|
if (strcmp(lvalue, "enable") == 0) {
|
|
|
|
|
if (sblock.fs_flags & FS_MULTILABEL) {
|
|
|
|
|
warnx("%s remains unchanged as enabled", name);
|
|
|
|
|
} else {
|
|
|
|
|
sblock.fs_flags |= FS_MULTILABEL;
|
|
|
|
|
warnx("%s set", name);
|
|
|
|
|
}
|
|
|
|
|
} else if (strcmp(lvalue, "disable") == 0) {
|
|
|
|
|
if ((~sblock.fs_flags & FS_MULTILABEL) ==
|
|
|
|
|
FS_MULTILABEL) {
|
|
|
|
|
warnx("%s remains unchanged as disabled",
|
|
|
|
|
name);
|
|
|
|
|
} else {
|
|
|
|
|
sblock.fs_flags &= ~FS_MULTILABEL;
|
2002-10-16 05:03:40 +00:00
|
|
|
warnx("%s cleared", name);
|
2002-10-14 19:52:12 +00:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
2000-12-10 20:59:30 +00:00
|
|
|
if (mflag) {
|
|
|
|
|
name = "minimum percentage of free space";
|
|
|
|
|
if (sblock.fs_minfree == mvalue) {
|
|
|
|
|
warnx("%s remains unchanged as %d%%", name, mvalue);
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
warnx("%s changes from %d%% to %d%%",
|
|
|
|
|
name, sblock.fs_minfree, mvalue);
|
|
|
|
|
sblock.fs_minfree = mvalue;
|
|
|
|
|
if (mvalue >= MINFREE && sblock.fs_optim == FS_OPTSPACE)
|
|
|
|
|
warnx(OPTWARN, "time", ">=", MINFREE);
|
|
|
|
|
if (mvalue < MINFREE && sblock.fs_optim == FS_OPTTIME)
|
|
|
|
|
warnx(OPTWARN, "space", "<", MINFREE);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
if (nflag) {
|
|
|
|
|
name = "soft updates";
|
|
|
|
|
if (strcmp(nvalue, "enable") == 0) {
|
2001-04-13 23:54:49 +00:00
|
|
|
if (sblock.fs_flags & FS_DOSOFTDEP) {
|
2000-12-10 20:59:30 +00:00
|
|
|
warnx("%s remains unchanged as enabled", name);
|
2001-04-13 23:54:49 +00:00
|
|
|
} else if (sblock.fs_clean == 0) {
|
|
|
|
|
warnx("%s cannot be enabled until fsck is run",
|
|
|
|
|
name);
|
2000-12-10 20:59:30 +00:00
|
|
|
} else {
|
|
|
|
|
sblock.fs_flags |= FS_DOSOFTDEP;
|
|
|
|
|
warnx("%s set", name);
|
|
|
|
|
}
|
|
|
|
|
} else if (strcmp(nvalue, "disable") == 0) {
|
|
|
|
|
if ((~sblock.fs_flags & FS_DOSOFTDEP) == FS_DOSOFTDEP) {
|
|
|
|
|
warnx("%s remains unchanged as disabled", name);
|
|
|
|
|
} else {
|
|
|
|
|
sblock.fs_flags &= ~FS_DOSOFTDEP;
|
|
|
|
|
warnx("%s cleared", name);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
if (oflag) {
|
|
|
|
|
name = "optimization preference";
|
|
|
|
|
chg[FS_OPTSPACE] = "space";
|
|
|
|
|
chg[FS_OPTTIME] = "time";
|
|
|
|
|
if (sblock.fs_optim == ovalue) {
|
|
|
|
|
warnx("%s remains unchanged as %s", name, chg[ovalue]);
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
warnx("%s changes from %s to %s",
|
|
|
|
|
name, chg[sblock.fs_optim], chg[ovalue]);
|
|
|
|
|
sblock.fs_optim = ovalue;
|
|
|
|
|
if (sblock.fs_minfree >= MINFREE &&
|
|
|
|
|
ovalue == FS_OPTSPACE)
|
|
|
|
|
warnx(OPTWARN, "time", ">=", MINFREE);
|
|
|
|
|
if (sblock.fs_minfree < MINFREE &&
|
|
|
|
|
ovalue == FS_OPTTIME)
|
|
|
|
|
warnx(OPTWARN, "space", "<", MINFREE);
|
|
|
|
|
}
|
|
|
|
|
}
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
if (sflag) {
|
|
|
|
|
name = "expected number of files per directory";
|
|
|
|
|
if (sblock.fs_avgfpdir == svalue) {
|
|
|
|
|
warnx("%s remains unchanged as %d", name, svalue);
|
|
|
|
|
}
|
|
|
|
|
else {
|
|
|
|
|
warnx("%s changes from %d to %d",
|
|
|
|
|
name, sblock.fs_avgfpdir, svalue);
|
|
|
|
|
sblock.fs_avgfpdir = svalue;
|
|
|
|
|
}
|
|
|
|
|
}
|
2000-12-10 20:59:30 +00:00
|
|
|
|
2003-01-28 02:42:01 +00:00
|
|
|
if (sbwrite(&disk, Aflag) == -1)
|
|
|
|
|
goto err;
|
|
|
|
|
ufs_disk_close(&disk);
|
1999-01-20 01:22:39 +00:00
|
|
|
if (active) {
|
|
|
|
|
bzero(&args, sizeof(args));
|
2003-01-28 02:42:01 +00:00
|
|
|
if (mount("ufs", on,
|
1999-01-20 01:22:39 +00:00
|
|
|
stfs.f_flags | MNT_UPDATE | MNT_RELOAD, &args) < 0)
|
|
|
|
|
err(9, "%s: reload", special);
|
2002-08-21 18:11:48 +00:00
|
|
|
warnx("file system reloaded");
|
1999-01-20 01:22:39 +00:00
|
|
|
}
|
1994-05-26 06:35:07 +00:00
|
|
|
exit(0);
|
2003-01-28 02:42:01 +00:00
|
|
|
err:
|
|
|
|
|
if (disk.d_error != NULL)
|
|
|
|
|
errx(11, "%s: %s", special, disk.d_error);
|
|
|
|
|
else
|
|
|
|
|
err(12, "%s", special);
|
1994-05-26 06:35:07 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void
|
2003-01-20 21:15:02 +00:00
|
|
|
usage(void)
|
1994-05-26 06:35:07 +00:00
|
|
|
{
|
1998-08-03 06:41:20 +00:00
|
|
|
fprintf(stderr, "%s\n%s\n%s\n",
|
2002-10-15 15:30:55 +00:00
|
|
|
"usage: tunefs [-A] [-a enable | disable] [-e maxbpg] [-f avgfilesize]",
|
2002-10-14 19:52:12 +00:00
|
|
|
" [-l enable | disable] [-m minfree] [-n enable | disable]",
|
|
|
|
|
" [-o space | time] [-p] [-s avgfpdir] special | filesystem");
|
1994-05-26 06:35:07 +00:00
|
|
|
exit(2);
|
|
|
|
|
}
|
|
|
|
|
|
1995-06-25 17:46:13 +00:00
|
|
|
void
|
2003-01-20 21:15:02 +00:00
|
|
|
printfs(void)
|
1995-06-25 17:46:13 +00:00
|
|
|
{
|
2002-10-15 18:14:05 +00:00
|
|
|
warnx("ACLs: (-a) %s",
|
|
|
|
|
(sblock.fs_flags & FS_ACLS)? "enabled" : "disabled");
|
|
|
|
|
warnx("MAC multilabel: (-l) %s",
|
|
|
|
|
(sblock.fs_flags & FS_MULTILABEL)? "enabled" : "disabled");
|
2003-01-18 06:29:15 +00:00
|
|
|
warnx("soft updates: (-n) %s",
|
1998-03-08 09:59:44 +00:00
|
|
|
(sblock.fs_flags & FS_DOSOFTDEP)? "enabled" : "disabled");
|
1995-06-25 17:46:13 +00:00
|
|
|
warnx("maximum blocks per file in a cylinder group: (-e) %d",
|
|
|
|
|
sblock.fs_maxbpg);
|
Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.
His description of the problem and solution follow. My own tests show
speedups on typical filesystem intensive workloads of 5% to 12% which
is very impressive considering the small amount of code change involved.
------
One day I noticed that some file operations run much faster on
small file systems then on big ones. I've looked at the ffs
algorithms, thought about them, and redesigned the dirpref algorithm.
First I want to describe the results of my tests. These results are old
and I have improved the algorithm after these tests were done. Nevertheless
they show how big the perfomance speedup may be. I have done two file/directory
intensive tests on a two OpenBSD systems with old and new dirpref algorithm.
The first test is "tar -xzf ports.tar.gz", the second is "rm -rf ports".
The ports.tar.gz file is the ports collection from the OpenBSD 2.8 release.
It contains 6596 directories and 13868 files. The test systems are:
1. Celeron-450, 128Mb, two IDE drives, the system at wd0, file system for
test is at wd1. Size of test file system is 8 Gb, number of cg=991,
size of cg is 8m, block size = 8k, fragment size = 1k OpenBSD-current
from Dec 2000 with BUFCACHEPERCENT=35
2. PIII-600, 128Mb, two IBM DTLA-307045 IDE drives at i815e, the system
at wd0, file system for test is at wd1. Size of test file system is 40 Gb,
number of cg=5324, size of cg is 8m, block size = 8k, fragment size = 1k
OpenBSD-current from Dec 2000 with BUFCACHEPERCENT=50
You can get more info about the test systems and methods at:
http://www.ptci.ru/gluk/dirpref/old/dirpref.html
Test Results
tar -xzf ports.tar.gz rm -rf ports
mode old dirpref new dirpref speedup old dirprefnew dirpref speedup
First system
normal 667 472 1.41 477 331 1.44
async 285 144 1.98 130 14 9.29
sync 768 616 1.25 477 334 1.43
softdep 413 252 1.64 241 38 6.34
Second system
normal 329 81 4.06 263.5 93.5 2.81
async 302 25.7 11.75 112 2.26 49.56
sync 281 57.0 4.93 263 90.5 2.9
softdep 341 40.6 8.4 284 4.76 59.66
"old dirpref" and "new dirpref" columns give a test time in seconds.
speedup - speed increasement in times, ie. old dirpref / new dirpref.
------
Algorithm description
The old dirpref algorithm is described in comments:
/*
* Find a cylinder to place a directory.
*
* The policy implemented by this algorithm is to select from
* among those cylinder groups with above the average number of
* free inodes, the one with the smallest number of directories.
*/
A new directory is allocated in a different cylinder groups than its
parent directory resulting in a directory tree that is spreaded across
all the cylinder groups. This spreading out results in a non-optimal
access to the directories and files. When we have a small filesystem
it is not a problem but when the filesystem is big then perfomance
degradation becomes very apparent.
What I mean by a big file system ?
1. A big filesystem is a filesystem which occupy 20-30 or more percent
of total drive space, i.e. first and last cylinder are physically
located relatively far from each other.
2. It has a relatively large number of cylinder groups, for example
more cylinder groups than 50% of the buffers in the buffer cache.
The first results in long access times, while the second results in
many buffers being used by metadata operations. Such operations use
cylinder group blocks and on-disk inode blocks. The cylinder group
block (fs->fs_cblkno) contains struct cg, inode and block bit maps.
It is 2k in size for the default filesystem parameters. If new and
parent directories are located in different cylinder groups then the
system performs more input/output operations and uses more buffers.
On filesystems with many cylinder groups, lots of cache buffers are
used for metadata operations.
My solution for this problem is very simple. I allocate many directories
in one cylinder group. I also do some things, so that the new allocation
method does not cause excessive fragmentation and all directory inodes
will not be located at a location far from its file's inodes and data.
The algorithm is:
/*
* Find a cylinder group to place a directory.
*
* The policy implemented by this algorithm is to allocate a
* directory inode in the same cylinder group as its parent
* directory, but also to reserve space for its files inodes
* and data. Restrict the number of directories which may be
* allocated one after another in the same cylinder group
* without intervening allocation of files.
*
* If we allocate a first level directory then force allocation
* in another cylinder group.
*/
My early versions of dirpref give me a good results for a wide range of
file operations and different filesystem capacities except one case:
those applications that create their entire directory structure first
and only later fill this structure with files.
My solution for such and similar cases is to limit a number of
directories which may be created one after another in the same cylinder
group without intervening file creations. For this purpose, I allocate
an array of counters at mount time. This array is linked to the superblock
fs->fs_contigdirs[cg]. Each time a directory is created the counter
increases and each time a file is created the counter decreases. A 60Gb
filesystem with 8mb/cg requires 10kb of memory for the counters array.
The maxcontigdirs is a maximum number of directories which may be created
without an intervening file creation. I found in my tests that the best
performance occurs when I restrict the number of directories in one cylinder
group such that all its files may be located in the same cylinder group.
There may be some deterioration in performance if all the file inodes
are in the same cylinder group as its containing directory, but their
data partially resides in a different cylinder group. The maxcontigdirs
value is calculated to try to prevent this condition. Since there is
no way to know how many files and directories will be allocated later
I added two optimization parameters in superblock/tunefs. They are:
int32_t fs_avgfilesize; /* expected average file size */
int32_t fs_avgfpdir; /* expected # of files per directory */
These parameters have reasonable defaults but may be tweeked for special
uses of a filesystem. They are only necessary in rare cases like better
tuning a filesystem being used to store a squid cache.
I have been using this algorithm for about 3 months. I have done
a lot of testing on filesystems with different capacities, average
filesize, average number of files per directory, and so on. I think
this algorithm has no negative impact on filesystem perfomance. It
works better than the default one in all cases. The new dirpref
will greatly improve untarring/removing/coping of big directories,
decrease load on cvs servers and much more. The new dirpref doesn't
speedup a compilation process, but also doesn't slow it down.
Obtained from: Grigoriy Orlov <gluk@ptci.ru>
2001-04-10 08:38:59 +00:00
|
|
|
warnx("average file size: (-f) %d",
|
|
|
|
|
sblock.fs_avgfilesize);
|
|
|
|
|
warnx("average number of files in a directory: (-s) %d",
|
|
|
|
|
sblock.fs_avgfpdir);
|
1995-06-25 17:46:13 +00:00
|
|
|
warnx("minimum percentage of free space: (-m) %d%%",
|
|
|
|
|
sblock.fs_minfree);
|
|
|
|
|
warnx("optimization preference: (-o) %s",
|
|
|
|
|
sblock.fs_optim == FS_OPTSPACE ? "space" : "time");
|
|
|
|
|
if (sblock.fs_minfree >= MINFREE &&
|
|
|
|
|
sblock.fs_optim == FS_OPTSPACE)
|
|
|
|
|
warnx(OPTWARN, "time", ">=", MINFREE);
|
|
|
|
|
if (sblock.fs_minfree < MINFREE &&
|
|
|
|
|
sblock.fs_optim == FS_OPTTIME)
|
|
|
|
|
warnx(OPTWARN, "space", "<", MINFREE);
|
|
|
|
|
}
|
