summaryrefslogtreecommitdiffstats
path: root/sbin/tunefs
Commit message (Collapse)AuthorAgeFilesLines
* Implement NFSv4 ACL support for UFS.trasz2009-12-212-11/+54
| | | | Reviewed by: rwatson
* The tunefs utility does not work on active filesystems.remko2009-10-211-2/+2
| | | | | | PR: docs/139705 Submitted by: Warren Block <wblock at wonkity dot com> Approved by: imp (mentor, implicit)
* Switch the default WARNS level for sbin/ to 6.ru2009-10-191-0/+1
| | | | Submitted by: Ulrich Spörlein
* Slightly improve gjournal documentation.trasz2009-04-291-1/+2
| | | | Reviewed by: pjd
* o s/filesystem/file system/g.maxim2007-09-231-2/+2
| | | | | | Pointed out by: ru Approved by: re (bmah) MFC after: 3 days
* o You have to reboot the system after tuning softupdates on the rootmaxim2007-08-121-1/+3
| | | | | | | filesystem on to make SU work. Approved by: re (hrs) MFC after: 1 week
* Add -J flag to both newfs(8) and tunefs(8) which allows to enable gjournalpjd2006-10-312-7/+45
| | | | | | | | support. I left -j flag for UFS journal implementation which we may gain at some point. Sponsored by: home.pl
* Expand *n't contractions.ru2005-02-131-1/+1
|
* Sort sections.ru2005-01-181-5/+5
|
* Remove advertising clause from University of California Regent's license,markm2004-04-092-8/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* Fixed some style bugs in the residue of rev.1.14 (mainly initialization inbde2004-03-261-26/+23
| | | | declarations, uncuddled elses and excessive braces).
* Fixed some style bugs in or related to rev.1.13 (mainly misindentation ofbde2004-03-261-109/+128
| | | | the getopt() case statement).
* Remove another reference to ffsinfo.8brueffer2003-06-171-3/+1
|
* Remove references to ffsinfo(8) for now. It was disconnected frombrueffer2003-06-171-1/+0
| | | | the build almost a year ago.
* Use __FBSDID() to quiet GCC 3.3 warnings.obrien2003-05-031-4/+4
|
* Sort options.ru2003-02-232-22/+22
|
* Bring in support for volume labels to the filesystem utilities.gordon2003-02-012-8/+35
| | | | Reviewed by: mckusick
* Fix problems with how libufs was used, with regard to mounted/active fs's,jmallett2003-01-281-32/+16
| | | | | in the new world order of libufs, where we also do statfs, and add a missing close.
* Added UFS library to the bsd.libnames.mk namespace.ru2003-01-231-1/+1
|
* Make tunefs use libufs, it seems to do well enough for printing / settingjmallett2003-01-202-108/+15
| | | | things.
* Consistentify output whitespace.jmallett2003-01-181-1/+1
|
* Create a new 32-bit fs_flags word in the superblock. Add code to movemckusick2002-11-271-1/+1
| | | | | | | | | | | | | | | | | the old 8-bit fs_old_flags to the new location the first time that the filesystem is mounted by a new kernel. One of the unused flags in fs_old_flags is used to indicate that the flags have been moved. Leave the fs_old_flags word intact so that it will work properly if used on an old kernel. Change the fs_sblockloc superblock location field to be in units of bytes instead of in units of filesystem fragments. The old units did not work properly when the fragment size exceeeded the superblock size (8192). Update old fs_sblockloc values at the same time that the flags are moved. Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk> Sponsored by: DARPA & NAI Labs.
* s/clear/cleared/ for consistency (sigh)rwatson2002-10-161-2/+2
| | | | Reported by: dd
* Spell 'set' as 'cleared' where appropriate.rwatson2002-10-151-2/+2
|
* Teach tunefs to print the ACL and multilabel flag information whenrwatson2002-10-151-0/+4
| | | | | | | inspecting a superblock. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Correct some of the style problems in this file:rwatson2002-10-152-10/+10
| | | | | | | | | I introduced a style problem when I sorted 'a' before 'A'; our preferred order sorts 'A' first. Correct. Use .Cm instead of .Ar. Submitted by: bde
* Introduce -a [enable|disable] and -l [enable|disable] flags to the tunefsrwatson2002-10-142-7/+73
| | | | | | | | command, permitting it to set FS_ACLS and FS_MULTILABEL administrative flags on UFS file systems. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Removed vestiges of the -a and -d options.bde2002-09-061-5/+3
| | | | Fixed other bugs in the usage message so that it matches the man page.
* Remove the -a maxcontig option, the kernel doesn't inspect fs_maxcontigphk2002-09-062-27/+3
| | | | | | anymore. Sponsored by: DARPA & NAI Labs.
* Fix some 'SYNOPSIS' and 'usage' messages.trhodes2002-08-271-1/+1
|
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-212-18/+18
|
* mdoc(7) police: laundry.ru2002-08-131-17/+16
|
* The .Nm utility.charnier2002-07-061-3/+4
|
* Don't say that an umounted filesystem is required for -n. An unmountedbde2002-06-211-1/+0
| | | | | filesystem is no more or less required for -n than for any other option. The previous commit clarified the actual requirement.
* This commit adds basic support for the UFS2 filesystem. The UFS2mckusick2002-06-212-57/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | filesystem expands the inode to 256 bytes to make space for 64-bit block pointers. It also adds a file-creation time field, an ability to use jumbo blocks per inode to allow extent like pointer density, and space for extended attributes (up to twice the filesystem block size worth of attributes, e.g., on a 16K filesystem, there is space for 32K of attributes). UFS2 fully supports and runs existing UFS1 filesystems. New filesystems built using newfs can be built in either UFS1 or UFS2 format using the -O option. In this commit UFS1 is the default format, so if you want to build UFS2 format filesystems, you must specify -O 2. This default will be changed to UFS2 when UFS2 proves itself to be stable. In this commit the boot code for reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c) as there is insufficient space in the boot block. Once the size of the boot block is increased, this code can be defined. Things to note: the definition of SBSIZE has changed to SBLOCKSIZE. The header file <ufs/ufs/dinode.h> must be included before <ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and ufs_lbn_t. Still TODO: Verify that the first level bootstraps work for all the architectures. Convert the utility ffsinfo to understand UFS2 and test growfs. Add support for the extended attribute storage. Update soft updates to ensure integrity of extended attribute storage. Switch the current extended attribute interfaces to use the extended attribute storage. Add the extent like functionality (framework is there, but is currently never used). Sponsored by: DARPA & NAI Labs. Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
* mdoc(7) police: markup nits.ru2002-05-291-1/+1
|
* more file system > filesystemtrhodes2002-05-161-3/+3
|
* Sigh, more BBSIZE related breakage.phk2002-05-121-0/+1
| | | | Sponsored by: DARPA & NAI Labs.
* 'file system' > filesystemtrhodes2002-05-061-12/+18
| | | | | | | add FILES section. PR: 34239 Submitted by: Gary W. Swearingen <swear@blarg.net>
* Expand the reserved space section. Explain how the amount of reservedkeramida2002-04-161-4/+12
| | | | | | space can affect performance. Submitted by: David Schultz <dschultz@uclink.Berkeley.EDU>
* o remove __Pimp2002-03-211-6/+6
| | | | o remove main prototype
* tunefs no longer outputs a warning if one tries to set soft-updates ondd2002-01-071-21/+0
| | | | | | | an unmounted filesystem. PR: 32266 Submitted by: Maxim Konovalov <maxim@macomnet.ru>
* Default to WARNS=2.obrien2001-12-041-1/+0
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* Don't require that the special/filesystem argument translates intoiedowse2001-09-301-5/+4
| | | | | | | | | | | a block or character device; the rest of tunefs works just fine on filesystem images in regular files. Instead, if getfsfile() failed and if the specified filesystem is a directory then print a more useful "unknown file system" error. Also, _PATH_DEV already contains a trailing slash, so don't add another one when constructing a device path, and use errx() instead of err() in a case where errno is meangingless.
* sprintf -> snprintfkris2001-07-241-1/+2
| | | | | Obtained from: OpenBSD MFC After: 1 week
* Constify, de-register-ify, and set WARNS=2.dd2001-07-152-12/+15
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* Do not allow the soft updates flag to be set if the filesystem is dirty.mckusick2001-04-131-1/+4
| | | | | | | | | | | Because the kernel will allow the mounting of unclean filesystems when the soft updates flag is set, it is important that only soft updates style inconsistencies (missing blocks and inodes) be present. Otherwise a panic may ensue. It is also important that the filesystem be in a clean state when the soft updates flag is set because the background fsck uses the fact that the flag is set to indicate that it is safe to run. If background fsck encounters non-soft updates style inconsistencies, it will exit with unexpected inconsistencies.
* Add information about the new options to newfs and tunefs which set thenik2001-04-101-0/+6
| | | | | expected average file size and number of files per directory. Could do with some fleshing out.
* Directory layout preference improvements from Grigoriy Orlov <gluk@ptci.ru>.mckusick2001-04-101-7/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
OpenPOWER on IntegriCloud