Home | History | Annotate | Download | only in newfs
History log of /src/sbin/newfs/newfs.8
RevisionDateAuthorComments
 1.86  17-Nov-2022  chs Restore backward compatibility of UFS2 with previous NetBSD releases by
disabling support in UFS2 for extended attributes (including ACLs).
Add a new variant of UFS2 called "UFS2ea" that does support extended attributes.
Add new fsck_ffs operations "-c ea" and "-c no-ea" to convert file systems
from UFS2 to UFS2ea and vice-versa (both of which delete all existing extended
attributes in the process).
 1.85  13-Apr-2019  maya Omit mention of old vnd(4) bug, now resolved.

Via elge, thanks.
 1.84  03-Jul-2017  wiz branches: 1.84.6;
Remove workaround for ancient HTML generation code.
 1.83  30-Jun-2012  tsutsui Use 32KB/4KB for default block/fragment size on >= 128 GB partitions
for modern AFT disks. No particular comments against PR install/46629.
 1.82  14-May-2011  dholland branches: 1.82.4; 1.82.6;
Improve documentation of FFS formats and format levels from PR 32100.
Prompted also by recent discussion on tech-kern. Bump date.
 1.81  06-Mar-2011  wiz New sentence, new line.
 1.80  06-Mar-2011  bouyer merge the bouyer-quota2 branch. This adds a new on-disk format
to store disk quota usage and limits, integrated with ffs
metadata. Usage is checked by fsck_ffs (no more quotacheck)
and is covered by the WAPBL journal. Enabled with kernel
option QUOTA2 (added where QUOTA was enabled in kernel config files),
turned on with tunefs(8) on a per-filesystem
basis. mount_mfs(8) can also turn quotas on.

See http://mail-index.netbsd.org/tech-kern/2011/02/19/msg010025.html
for details.
 1.79  09-Aug-2010  wiz branches: 1.79.2;
Sort option descriptions.
 1.78  09-Aug-2010  pooka Add -G, which turns consistency check errors in warnings. The
current testing purpose is to create a file system with
block size > MAXPHYS.

(the check doesn't make that much sense anyway in these days of
mobile file systems, since we're interested in MAXPHYS where we
attempt to mount the file system, not where we happen to create it)
 1.77  21-Feb-2010  wiz Call the file system "ext2" consistently. Suggested by tsutsui.
 1.76  18-Feb-2010  wiz Pull over some of Jason McIntyre's fixes for newfs_ext2fs.
Suggested by tsutsui.
 1.75  01-Dec-2009  pooka Add note saying that special must be a raw device.
PR bin/42391
 1.74  01-Jul-2009  uwe G/c sentence fragment left over from vinum reference (forgotten in 1.69).
Noticed by bad@ in PR bin/41652
 1.73  10-May-2009  lukem Note that FFSv1 is also known as FFS, UFS, or UFS1.
Note that FFSv2 is also known as UFS2.
Add a reference to Kirk's BSDcon03 paper on UFS2.
 1.72  01-Aug-2008  simonb branches: 1.72.4;
Handle 't' suffix for terabytes for number arguments.
 1.71  08-Mar-2008  reinoud branches: 1.71.4;
Fix small documentation bug as reported in PR#38192 :

FFS -> FFSv1
UFS2 -> FFSv2
 1.70  10-Dec-2007  tsutsui branches: 1.70.4; 1.70.6;
Add Xref newfs_ext2fs(8).
 1.69  25-Feb-2006  christos branches: 1.69.4; 1.69.6; 1.69.10; 1.69.12; 1.69.14;
remove vinum reference.
 1.68  15-Jan-2006  dsl Add a '-V verbose' option that controls the amount of info writen to stdout.
0: No output. Default for mount_mfs unless -N specified
1: Output size of partition and cylinder groups.
2: Follow with a progress-bar line of dots (scaled to finish at RH margin)
3: Include a single line of alternate suberblock addresses before progress
bar. Default for newfs.
4: Output lots of lines of alternate superblock numbers that scroll madly
up the screen.
If -N given, newfs/mount_mfs exits before displaying any progress bar.
Output constrained (almost always) to 1 column less than the terminal width.
 1.67  27-Dec-2005  hubertf Xref newfs_msdos, noted by rabioli on Freenode #NetBSD
 1.66  24-Jun-2005  wiz Bump date for previous.
 1.65  24-Jun-2005  peter Note that flag -a is obsolete. Thanks to Darrin B. Jewell.
Should fix PR/26883 from Hauke Fath.
 1.64  25-Jun-2004  wiz branches: 1.64.2;
Minimally document -d; addresses second part of
PR 25914 by Kouichirou Hiratsuka.
 1.63  01-Nov-2003  wiz eg -> e.g., vinum -> Xr vinum 4.
 1.62  01-Nov-2003  dsl Use fstat(2) to get the partition size (falling back to the label on old
kernels) so that newfs works on vinum (and similar).
Kill the -V hack for vinum.
Don't bother faking up a label for -F and mfs, nothing is needed from it.
Ignore label if special doesn't match DISKPART(sb.st_rdev);
Simplifly logic for default block/frag sizes.
Update man page to match.
WARNS=3.
 1.61  10-Oct-2003  wiz All single letter options are usually combined; add -V to the others.
 1.60  10-Oct-2003  grant bump date for last
 1.59  10-Oct-2003  grog Decribe the V flag.
 1.58  09-Oct-2003  dbj calculate "-s size" values after sectorsize has been fully determined
extend "-s size" argument to allow negative sizes to represent value to
subtract from diskalbel partition size
 1.57  11-Sep-2003  dsl Change date on man pages
 1.56  11-Sep-2003  dsl Make mkfs -N work again (was trying to read filesystem).
Correct calculation of number of inodes from density for small filesystems.
Add a '-n inodes' option so that the desired number of inodes can be
explicitly given - init needs this for mfs /dev, -i density is too crude.
 1.55  03-Sep-2003  dsl fsirand is no longer needed.
 1.54  12-Aug-2003  wiz Bump date for last.
 1.53  12-Aug-2003  dsl Mention and cross reference newfs_lfs and makefs.
 1.52  07-Aug-2003  agc Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22308, verified by myself.
 1.51  03-Apr-2003  wiz Sort options; mention -O default; grammar improvements; use more macros.
 1.50  03-Apr-2003  fvdl The -r option is no more, so delete it from the synopsis line too.
 1.49  03-Apr-2003  tron Document extended "-O" option after UFS2 import.
 1.48  02-Apr-2003  fvdl Add support for UFS2. UFS2 is an enhanced FFS, adding support for
64 bit block pointers, extended attribute storage, and a few
other things.

This commit does not yet include the code to manipulate the extended
storage (for e.g. ACLs), this will be done later.

Originally written by Kirk McKusick and Network Associates Laboratories for
FreeBSD.
 1.47  25-Feb-2003  wiz .Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.
 1.46  12-Oct-2002  wiz Remove some unnecessary ``\&''. Add an 'n' between an 'a' and an 'A'.
 1.45  01-Oct-2002  wiz New sentence, new line. By Robert Elz with minimal fixes.
 1.44  28-Sep-2002  dbj Add support for the Apple UFS variation on ffs
This is the bulk of PR #17345

The general approach is to use a run time deteriminable value
for DIRBLKSIZ. Additional allowances are included for using
MAXSYMLINKLEN with FS_42INODEFMT and a shift in the cylinder group
cluster summary count array. Support is added for managing
the Apple UFS volume label.
 1.43  20-Aug-2002  wiz Drop superfluous Ns.
 1.42  06-Apr-2002  dsainty Reverted a small part of 1.30, removing full stops that accidentally got added
in the middle of sentences.
 1.41  20-Feb-2002  lukem change the default back to checking the file system type is '4.2BSD',
and add -I to ignore this check. per discussion with thorpej.
 1.40  08-Feb-2002  ross Generate <>& symbolically. I'm avoiding .../dist/... directories for now.
 1.39  04-Jan-2002  lukem move mount_mfs(8) into separate man page
 1.38  31-Dec-2001  lukem document that default block-size, frag-size, and bytes-per-inode are
now dependent upon file system size
 1.37  30-Dec-2001  lukem Fixes from and/or inspired by FreeBSD:
- Change the default cpg from 16 to 65536, which effectively means
that the largest allowable value for cpg will be computed if it's
not specified with -c or in the disklabel for that partition.
This is much more convenient for users.
- Improve the description of the defaults for various options
 1.36  21-Nov-2001  lukem - For mount_mfs, always ignore the `special' field and just fake up
the label instead. The previous change to use opendisk() prevented
this from working with special fields such as `/dev/wd0b', and this
new method is arguably cleaner anyway. Fixes [misc/14654]
- Don't bother supporting -T for mount_mfs anymore, since it's
superfluous. The option still works (for compatibility reasons), but
it's just ignored and not documented anymore.
- Use an RPM of 10000 instead of 3600 for the fake label (why not :-)
 1.35  16-Nov-2001  wiz Sort SEE ALSO, whitespace nits.
 1.34  16-Nov-2001  lukem - Without -F, use opendisk(3) to find the raw device
- With -F, relax the restriction that the filesystem must be a regular file
 1.33  06-Sep-2001  lukem Incorporate the enhanced ffs_dirpref() by Grigoriy Orlov, as found in
FreeBSD (three commits; the initial work, man page updates, and a fix
to ffs_reload()), with the following differences:
- Be consistent between newfs(8) and tunefs(8) as to the options which
set and control the tuning parameters for this work (avgfilesize & avgfpdir)
- Use u_int16_t instead of u_int8_t to keep track of the number of
contiguous directories (suggested by Chuck Silvers)
- Work within our FFS_EI framework
- Ensure that fs->fs_maxclusters and fs->fs_contigdirs don't point to
the same area of memory

The new algorithm has a marked performance increase, especially when
performing tasks such as untarring pkgsrc.tar.gz, etc.

The original FreeBSD commit messages are attached:

=====
mckusick 2001/04/10 01:39:00 PDT
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>
=====

=====
iedowse 2001/04/23 17:37:17 PDT
Pre-dirpref versions of fsck may zero out the new superblock fields
fs_contigdirs, fs_avgfilesize and fs_avgfpdir. This could cause
panics if these fields were zeroed while a filesystem was mounted
read-only, and then remounted read-write.

Add code to ffs_reload() which copies the fs_contigdirs pointer
from the previous superblock, and reinitialises fs_avgf* if necessary.

Reviewed by: mckusick
=====

=====
nik 2001/04/10 03:36:44 PDT
Add information about the new options to newfs and tunefs which set the
expected average file size and number of files per directory. Could do
with some fleshing out.
=====
 1.32  31-Aug-2001  lukem fix a couple of typos in option descriptions
 1.31  30-Aug-2001  lukem replace mkfs reference with sentence describing what newfs does (from freebsd)
 1.30  29-Jul-2001  lukem * add -F option: enable creation of file system in a regular file. a "fake"
disklabel is created as per mfs on "swap".
* add -Z option: pre-zero the -F image file before use. this is necessary if
the image is to be used with vnd(4) because by default the files created
with -F have "holes" and vnd doesn't cope with that.
* support 'k', 'm', 'g' suffixes for all options which take numeric arguments.
provide strsuftoi() which performs the parsing mechanism.
* improve man page description of various options
* replace "filesystem" with "file system"
* when displaying usage for mfs, only list mfs options
* minor KNF and WARNS=2 cleanups
 1.29  07-Jun-2001  mrg s/primary swap area/first swap area/
 1.28  05-Jun-2001  wiz Drop arguments of .Os.
 1.27  03-Apr-2001  wiz Don't xref format(8) -- the man pages we have for it (hp300/vax) don't
seem very interesting at all, if not even obsolete.
Whitespace fixes while I'm here.
 1.26  02-Mar-2001  ad Fix typo.
 1.25  01-Dec-2000  simonb For mount_mfs, allow an 'm' suffix to the file system size option to
specify the size of the mfs in megabytes.

Inspired by the Solaris tmpfs "-o size=sz" option.
 1.24  16-May-1999  ad branches: 1.24.8;
Add NOTES section. Indicate that fstype in disklabel should be set to 4.2BSD.
 1.23  16-Mar-1999  wrstuden Modify newfs so that the root node (and lost+found dir, if created)
of the new fs has uid.gid equal to the euid.egid of the process
which made it. This change permits users who have write access to
a device (say a floppy) to create a filesystem that, when mounted,
they have write access to.

This change closes PR bin/5990 from jbernard@ox.mines.edu, and is also the
change requested in PR bin/6276 from "Charles M. Hannum" <mycroft@netbsd.org>
 1.22  07-Mar-1999  mycroft Clean up SYNOPSIS formatting.
 1.21  07-May-1998  mycroft Add a reference to fsirand(8).
 1.20  29-Apr-1998  fair fix bad .Xr references
 1.19  18-Mar-1998  bouyer Allow creation of non-native byteorder FFS (via the '-B' option).
 1.18  06-Feb-1998  perry macroize BSD, NetBSD, FreeBSD and misc cleanup
 1.17  16-Sep-1997  lukem * resolve conflicts from lite-2 import
* use int32_t instead of long
 1.16  15-Sep-1997  lukem * getopt returns -1 not EOF
* fix .Nm usage
 1.15  08-Mar-1997  mouse alternate -> alternative, per PR 2643
 1.14  26-Dec-1996  mikel eliminate obsolete reference to mkfs(8);
from Klaus Klein <kleink@layla.inka.de>.
also fixed buggy -a flag lines, reference fsck_ffs(8) instead of fsck(8).
 1.13  06-Jun-1996  mrg update to reality. from mike long (pr#2517)
 1.12  18-Mar-1995  cgd convert to new RCS Id conventions; reduce my headache
 1.11  18-Dec-1994  cgd adjust the documentation to note that 'swap' can be used instead of a dev.
 1.10  01-Dec-1994  mycroft Use defaults that are more reasonable for modern disks, and document the `-n'
option.
 1.9  16-Jul-1994  jtc Change mfs in Synopsis to mount_mfs.
 1.8  08-Jun-1994  mycroft branches: 1.8.2;
Update from 4.4-Lite, with local changes.
 1.7  20-Apr-1994  cgd back to 10%, per mkm
 1.6  12-Apr-1994  cgd 10 -> 5
 1.5  01-Aug-1993  mycroft Add RCS indentifiers.
 1.4  28-Jul-1993  cgd incorporate changes from 0-9-base to 0-9-ALPHA
 1.3  23-Mar-1993  cgd branches: 1.3.2;
changed "Id" to "Header" for rcsids
 1.2  22-Mar-1993  cgd added rcs ids to all files
 1.1  21-Mar-1993  cgd branches: 1.1.1;
Initial revision
 1.1.1.3  16-Sep-1997  lukem imported from lite-2
 1.1.1.2  13-Jun-1994  mycroft Import 4.4-Lite version.
 1.1.1.1  21-Mar-1993  cgd initial import of 386bsd-0.1 sources
 1.3.2.1  20-Jul-1993  cgd change all refs to "mfs" to be to "mount_mfs" as is appropriate
 1.8.2.1  20-Jul-1994  cgd update from trunk.
 1.24.8.3  25-Nov-2001  he Pull up revision 1.33 (via patch, requested by lukem):
Pull in enhanced ffs_dirpref() algorithm, which provides a
substantial performance improvement through better locality
between parent/child directories and their files, and by easing
the pressure on the buffer cache for metadata operations.
 1.24.8.2  24-Nov-2001  he Pull up revisions 1.25-1.26,1.28-1.29,1.31 (requested by lukem):
Jumbo pullup for newfs:
o allow ``m'' suffix in MFS size
o replace ``filesystem'' with ``file system''
o manual page typos and other corrections
 1.24.8.1  04-Apr-2001  he Pull up revision 1.27 (requested by wiz):
Don't xref format(8) -- the man pages we have for it (hp300/vax) don't
seem very interesting at all, if not even obsolete.
Also some whitespace fixes.
 1.64.2.1  29-Dec-2005  riz Pull up following revision(s) (requested by hubertf in ticket #1073):
sbin/newfs/newfs.8: revision 1.67 via patch
Xref newfs_msdos, noted by rabioli on Freenode #NetBSD
 1.69.14.1  09-Mar-2008  bouyer Pull up following revision(s) (requested by reinoud in ticket #1099):
sbin/newfs/newfs.8: revision 1.71
Fix small documentation bug as reported in PR#38192 :
FFS -> FFSv1
UFS2 -> FFSv2
 1.69.12.1  27-Dec-2007  mjf Sync with HEAD.
 1.69.10.2  23-Mar-2008  matt sync with HEAD
 1.69.10.1  09-Jan-2008  matt sync with HEAD
 1.69.6.1  03-Jun-2008  skrll Sync with netbsd-4.
 1.69.4.1  09-Mar-2008  bouyer Pull up following revision(s) (requested by reinoud in ticket #1099):
sbin/newfs/newfs.8: revision 1.71
Fix small documentation bug as reported in PR#38192 :
FFS -> FFSv1
UFS2 -> FFSv2
 1.70.6.2  28-Sep-2008  mjf Sync with HEAD.
 1.70.6.1  03-Apr-2008  mjf Sync with HEAD.
 1.70.4.1  24-Mar-2008  keiichi sync with head.
 1.71.4.1  18-Sep-2008  wrstuden Sync with wrstuden-revivesa-base-2.
 1.72.4.1  13-May-2009  jym Sync with HEAD.

Third (and last) commit. See http://mail-index.netbsd.org/source-changes/2009/05/13/msg221222.html
 1.79.2.1  20-Jan-2011  bouyer Snapshot of work in progress on a modernised disk quota system:
- new quotactl syscall (versionned for backward compat), which takes
as parameter a path to a mount point, and a prop_dictionary
(in plistref format) describing commands and arguments.
For each command, status and data are returned as a prop_dictionary.
quota commands features will be added to take advantage of this,
exporting quota data or getting quota commands as plists.

- new on disk-format storage (all 64bit wide), integrated to metadata for
ffs (and playing nicely with wapbl).
Quotas are enabled on a ffs filesystem via superblock flags.
tunefs(8) can enable or disable quotas.
On a quota-enabled filesystem, fsck_ffs(8) will track per-uid/gid
block and inode usages, and will check and update quotas in Pass 6.
quota usage and limits are stored in unliked files (one for users,
one for groups)l fsck_ffs(8) will create the files if needed, or
free them if needed. This means that after enabling or disabling
quotas on a filesystem; a fsck_ffs(8) run is required.
quotacheck(8) is not needed any more, on a unclean shutdown
fsck or journal replay will take care of fixing quotas.
newfs(8) can create a ready-to-mount quota-enabled filesystem
(superblock flags are set and quota inodes are created).
Other new features or semantic changes:
- default quota datas, applied to users or groups which don't already
have a quota entry
- per-user/group grace time (instead of a filesystem global one)
- 0 really means "nothing allowed at all", not "no limit".
If you want "no limit", set the limit to UQUAD_MAX (tools will
understand "unlimited" and "-")

A quota file is structured as follow:
it starts with a header, containing a few per-filesystem values,
and the default quota limits.
Quota entries are linked together as a simple list, each entry has a
pointer (as an offset withing the file) to the next.
The header has a pointer to a list of free quota entries, and
a hash table of in-use entries. The size of the hash table depends
on the filesystem block size (header+hash table should fit in the
first block). The file is not sparse and is a multiple of
filesystem block size (when the free quota entry list is empty a new
filesystem block is allocated). quota entries to not cross
filesystem block boundaries.

In memory, the kernel keeps a cache of recently used quota entries
as a reference to the block number, and offset withing the block.
The quota entry itself is keept in the buf cache.

fsck_ffs(8), tunefs(8) and newfs(8) supports are completed (with
related atf tests :)
The kernel can update disk usage and report it via quotactl(2).

Todo: enforce quotas limits (limits are not checked by kernel yet)
update repquota, edquota and rpc.rquotad to the new world
implement compat_50_quotactl ioctl.
update quotactl(2) man page

fsck_ffs required fixes so that allocating new blocks or inodes will
properly update the superblock and cg sumaries. This was not an issue up
to now because superblock and cg sumaries check happened last, but now
allocations or frees can happen in pass 6.
 1.82.6.1  05-Jul-2012  riz Pull up following revision(s) (requested by tsutsui in ticket #396):
sbin/newfs/newfs.8: revision 1.83
sbin/newfs/newfs.c: revision 1.111
distrib/utils/sysinst/label.c: revision 1.62
Use 32KB/4KB for default block/fragment size on >= 128 GB partitions
for modern AFT disks. No particular comments against PR install/46629.
 1.82.4.1  30-Oct-2012  yamt sync with head
 1.84.6.1  10-Jun-2019  christos Sync with HEAD

RSS XML Feed