| History log of /src/sys/ufs/ffs/ffs_bswap.c |
| Revision | | Date | Author | Comments |
| 1.40 |
| 09-Feb-2017 |
kre | Sprinkle in a pinch of const, not too much, just enough
to add a little strength without affecting the overall balance...
|
| 1.39 |
| 20-May-2015 |
riastradh | branches: 1.39.2; 1.39.4;
memcpy di_extb/db/ib separately. Noted by Coverity, CID 974636.
|
| 1.38 |
| 20-May-2015 |
riastradh | Don't (harmlessly) overrun di_db array; copy di_ib separately.
Noted by Coverity, CID 974635.
While here, simplify size calculation for memcpy.
|
| 1.37 |
| 09-Jun-2013 |
dholland | branches: 1.37.8; 1.37.10;
Remove lfs-only inumber field (and its supporting union) from struct
ufs1_dinode.
|
| 1.36 |
| 22-Jan-2013 |
dholland | Stuff UFS_ in front of a few of ufs's symbols to reduce namespace
pollution. Specifically:
ROOTINO -> UFS_ROOTINO
WINO -> UFS_WINO
NXADDR -> UFS_NXADDR
NDADDR -> UFS_NDADDR
NIADDR -> UFS_NIADDR
MAXSYMLINKLEN -> UFS_MAXSYMLINKLEN
MAXSYMLINKLEN_UFS[12] -> UFS[12]_MAXSYMLINKLEN (for consistency)
Sort out ext2fs's misuse of NDADDR and NIADDR; fortunately, these have
the same values in ext2fs and ffs.
No functional change intended.
|
| 1.35 |
| 06-Mar-2011 |
bouyer | branches: 1.35.4; 1.35.14;
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.34 |
| 19-Oct-2009 |
bouyer | branches: 1.34.4; 1.34.6; 1.34.8;
Remove closes 3 & 4 from my licence. Lots of thanks to Soren Jacobsen
for the booring work !
|
| 1.33 |
| 18-Jan-2009 |
lukem | fix -Wsign-compare issues
|
| 1.32 |
| 11-Dec-2005 |
christos | branches: 1.32.74; 1.32.84;
merge ktrace-lwp.
|
| 1.31 |
| 03-Jun-2005 |
dbj | the cluster summary must be swapped even for ufs2
|
| 1.30 |
| 02-Jun-2005 |
is | fix copy/paste/don'tupdate bug (fix from PR 22232 by Robert Elz).
|
| 1.29 |
| 26-Feb-2005 |
perry | branches: 1.29.2;
nuke trailing whitespace
|
| 1.28 |
| 25-May-2004 |
hannken | branches: 1.28.4; 1.28.6;
Add ffs internal snapshots. Written by Marshall Kirk McKusick for FreeBSD.
- Not enabled by default. Needs kernel option FFS_SNAPSHOT.
- Change parameters of ffs_blkfree.
- Let the copy-on-write functions return an error so spec_strategy
may fail if the copy-on-write fails.
- Change genfs_*lock*() to use vp->v_vnlock instead of &vp->v_lock.
- Add flag B_METAONLY to VOP_BALLOC to return indirect block buffer.
- Add a function ffs_checkfreefile needed for snapshot creation.
- Add special handling of snapshot files:
Snapshots may not be opened for writing and the attributes are read-only.
Use the mtime as the time this snapshot was taken.
Deny mtime updates for snapshot files.
- Add function transferlockers to transfer any waiting processes from
one lock to another.
- Add vfsop VFS_SNAPSHOT to take a snapshot and make it accessible through
a vnode.
- Add snapshot support to ls, fsck_ffs and dump.
Welcome to 2.0F.
Approved by: Jason R. Thorpe <thorpej@netbsd.org>
|
| 1.27 |
| 31-Dec-2003 |
dbj | branches: 1.27.4;
remove incorrect XXX comments I introduced a couple of days ago
|
| 1.26 |
| 31-Dec-2003 |
dbj | remove unused cs_numclusters field from struct csum_total
this avoids a potential future bug if it is ever used.
before this fix, fsck_ffs would check and fix this field to be zero
|
| 1.25 |
| 31-Dec-2003 |
dbj | reorder ffs_sb_swap to reflect actual order in superblock
add comments regarding historical field overlap
no functional change
|
| 1.24 |
| 31-Dec-2003 |
dbj | add fs_flags to ffs_sb_swap
|
| 1.23 |
| 30-Dec-2003 |
dbj | fix bugs in ffs_cg_swap for FS_42POSTBLFMT
|
| 1.22 |
| 27-Oct-2003 |
lukem | Overhaul how `build.sh tools' are used:
* Rename "config.h" to "nbtool_config.h" and
HAVE_CONFIG_H to HAVE_NBTOOL_CONFIG_H.
This makes in more obvious in the source when we're using
tools/compat/config.h versus "standard autoconf" config.h
* Consistently move the inclusion of nbtool_config.h to before
<sys/cdefs.h> so that the former can provide __RCSID() (et al),
and there's no need to protect those macros any more.
These changes should make it easier to "tool-ify" a program by adding:
#if HAVE_NBTOOL_CONFIG_H
#include "nbtool_config.h"
#endif
to the top of the source files (for the general case).
|
| 1.21 |
| 05-Oct-2003 |
bouyer | Remove references to University of California from my copyright notices.
|
| 1.20 |
| 16-Apr-2003 |
yamt | branches: 1.20.2;
use bswap32 and bswap64 correctly.
(fs_pendingblocks and fs_pendinginodes)
|
| 1.19 |
| 11-Apr-2003 |
enami | Make ffs_cg_swap() works even if same chunk is passed as new and old cg.
This is necessary to prevent newfs from dumping core when it is asked to
create a UFS1 file system of non-native endian.
|
| 1.18 |
| 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.17 |
| 31-Jan-2002 |
tv | These sources are pulled into makefs(8), so we need config.h and protection
for __KERNEL_RCSID().
|
| 1.16 |
| 18-Dec-2001 |
fvdl | Bring over fixes from FreeBSD that weren't incorporated yet, mainly
from Kirk McKusick. They implement taking pending block/inode frees
into account for the sake of correct statfs() numbers, and adding
a new softdep type (newdirblk) to correctly handle newly allocated
directory blocks.
Minor additional changes: 1) swap the newly introduced fs_pendinginodes
and fs_pendingblock fields in ffs_sb_swap, and 2) declare lkt_held
in the debug version of the softdep lock structure volatile, as it
can be modified from interrupt context #ifdef DEBUG.
|
| 1.15 |
| 30-Oct-2001 |
lukem | add __KERNEL_RCSID()
|
| 1.14 |
| 29-Oct-2001 |
lukem | ffs_sb_swap() fixes:
- calculate the offset and length of the postbl before byteswapping.
problem noted by der Mouse.
- use offsetof() to determine # of fields to calculate in initial
loop, rather than hard-coding in `52 fields'
- improve comments.
|
| 1.13 |
| 06-Sep-2001 |
lukem | branches: 1.13.4;
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.12 |
| 03-Sep-2001 |
lukem | deprecate fs_fscktime; we never used it.
in an effort to maintain compatibility with freebsd/openbsd/whatever,
i'm attempting to get the superblock format in sync, and freebsd uses
the int32_t at this position for `fs_pendinginodes'.
if we ever decide to implement fscktime functionality, we'll:
a) make sure to liaise with the other projects to reserve the same
spare field
b) actually implement the code this time ...
(this is also preparing us for other changes, like the new dirpref code)
|
| 1.11 |
| 17-Aug-2001 |
lukem | remove third argument (`int ns') from ffs_sb_swap(), and let ffs_sb_swap()
determine the endianness of the `struct fs *o' superblock from o->fs_magic
and set needswap as necessary, rather than trusting the caller to get
it right. invariably, almost every caller of ffs_sb_swap() was calling it
with ns set to the wrong value for ns anyway!
ansi KNF ffs_bswap.c declarations whilst here.
this fixes all sorts of problems when trying to use other-endian file systems,
notably the kernel trying to access memory *way* off, possibly corrupting or
panicing, and userland programs SEGVing and/or corrupting things (e.g,
"fsck_ffs -B" to swap a file system endianness).
whilst the previous rev of ffs_bswap.c (1.10, 2000/12/23) made this problem
worse, i suspect that the problem was always there and previous versions
just happened not to trash things at the wrong time.
FFS_EI should now be a lot more stable.
|
| 1.10 |
| 23-Dec-2000 |
enami | branches: 1.10.2; 1.10.6;
- 16 * 8 != 168
- offset should be endian independent.
|
| 1.9 |
| 23-Dec-2000 |
enami | Cosmetic changes
|
| 1.8 |
| 15-May-2000 |
bouyer | branches: 1.8.4;
Sync copyrigth notice.
|
| 1.7 |
| 18-Jan-2000 |
bouyer | Handle pre-FS_42POSTBLFMT. I now can mount an Ultrix file system on my
sparc without panic.
|
| 1.6 |
| 14-Sep-1999 |
thorpej | branches: 1.6.2; 1.6.8;
Need <string.h> for memcpy(3) prototype if building from userland.
|
| 1.5 |
| 09-Aug-1998 |
perry | branches: 1.5.6;
bzero->memset, bcopy->memcpy, bcmp->memcmp
|
| 1.4 |
| 13-Jun-1998 |
kleink | KNF, mostly of FFS_EI changes.
|
| 1.3 |
| 10-Jun-1998 |
kleink | KNF: only include one of <sys/{param,types}.h>, not both.
|
| 1.2 |
| 08-Jun-1998 |
ragge | Wrong include file order; caused compile error on vax.
|
| 1.1 |
| 18-Mar-1998 |
bouyer | Add support for reading/writing FFS in non-native byte order, conditioned
to "options FFS_EI". The superblock and inodes (without blk addr) are
byteswapped at disk read/write time, other metadatas are byteswapped
when used (as they are acceeded directly in the buffer cache).
This required the addition of a "um_flags" field to struct ufsmount.
ffs_bswap.c contains superblock and inode byteswap routines also used
by userland utilities.
|
| 1.5.6.1 |
| 18-Jan-2000 |
he | Pull up revision 1.7 (requested by bouyer):
Properly handle pre-FS_42POSTBLFMT file systems (e.g. Ultrix) in
the endian-independent file system code.
|
| 1.6.8.1 |
| 21-Dec-1999 |
wrstuden | Initial commit of recent changes to make DEV_BSIZE go away.
Runs on i386, needs work on other arch's. Main kernel routines should be
fine, but a number of the stand programs need help.
cd, fd, ccd, wd, and sd have been updated. sd has been tested with non-512
byte block devices. vnd, raidframe, and lfs need work.
Non 2**n block support is automatic for LKM's and conditional for kernels
on "options NON_PO2_BLOCKS".
|
| 1.6.2.2 |
| 05-Jan-2001 |
bouyer | Sync with HEAD
|
| 1.6.2.1 |
| 20-Nov-2000 |
bouyer | Update thorpej_scsipi to -current as of a month ago
|
| 1.8.4.5 |
| 25-Nov-2001 |
he | Pull up revision 1.14 (requested by lukem):
A few ffs_sb_swap() fixes.
|
| 1.8.4.4 |
| 25-Nov-2001 |
he | Pull up revision 1.13 (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.8.4.3 |
| 25-Nov-2001 |
he | Pull up revision 1.12 (requested by lukem):
Deprecate unused fs_fscktime.
|
| 1.8.4.2 |
| 25-Nov-2001 |
he | Pull up revision 1.11 (requested by lukem):
Call ffs_sb_swap() with the correct arguments. Fixes problems
with using other-endian file systems.
|
| 1.8.4.1 |
| 25-Nov-2001 |
he | Pull up revisions 1.9-1.10 (requested by lukem):
Offset should be endian independent. Some cosmetic changes.
|
| 1.10.6.4 |
| 11-Feb-2002 |
jdolecek | Sync w/ -current.
|
| 1.10.6.3 |
| 10-Jan-2002 |
thorpej | Sync kqueue branch with -current.
|
| 1.10.6.2 |
| 13-Sep-2001 |
thorpej | Update the kqueue branch to HEAD.
|
| 1.10.6.1 |
| 25-Aug-2001 |
thorpej | Merge Aug 24 -current into the kqueue branch.
|
| 1.10.2.5 |
| 28-Feb-2002 |
nathanw | Catch up to -current.
|
| 1.10.2.4 |
| 08-Jan-2002 |
nathanw | Catch up to -current.
|
| 1.10.2.3 |
| 14-Nov-2001 |
nathanw | Catch up to -current.
|
| 1.10.2.2 |
| 21-Sep-2001 |
nathanw | Catch up to -current.
|
| 1.10.2.1 |
| 24-Aug-2001 |
nathanw | Catch up with -current.
|
| 1.13.4.1 |
| 12-Nov-2001 |
thorpej | Sync the thorpej-mips-cache branch with -current.
|
| 1.20.2.5 |
| 10-Nov-2005 |
skrll | Sync with HEAD. Here we go again...
|
| 1.20.2.4 |
| 04-Mar-2005 |
skrll | Sync with HEAD.
Hi Perry!
|
| 1.20.2.3 |
| 21-Sep-2004 |
skrll | Fix the sync with head I botched.
|
| 1.20.2.2 |
| 18-Sep-2004 |
skrll | Sync with HEAD.
|
| 1.20.2.1 |
| 03-Aug-2004 |
skrll | Sync with HEAD
|
| 1.27.4.1 |
| 02-Jun-2005 |
riz | Pull up revision 1.30 (requested by is in ticket #1973):
fix copy/paste/don'tupdate bug (fix from PR 22232 by Robert Elz).
|
| 1.28.6.1 |
| 19-Mar-2005 |
yamt | sync with head. xen and whitespace. xen part is not finished.
|
| 1.28.4.1 |
| 29-Apr-2005 |
kent | sync with -current
|
| 1.29.2.1 |
| 02-Jun-2005 |
tron | Pull up revision 1.30 (requested by is in ticket #385):
fix copy/paste/don'tupdate bug (fix from PR 22232 by Robert Elz).
|
| 1.32.84.1 |
| 19-Jan-2009 |
skrll | Sync with HEAD.
|
| 1.32.74.2 |
| 11-Mar-2010 |
yamt | sync with head
|
| 1.32.74.1 |
| 04-May-2009 |
yamt | sync with head.
|
| 1.34.8.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.34.6.1 |
| 06-Jun-2011 |
jruoho | Sync with HEAD.
|
| 1.34.4.1 |
| 21-Apr-2011 |
rmind | sync with head
|
| 1.35.14.3 |
| 03-Dec-2017 |
jdolecek | update from HEAD
|
| 1.35.14.2 |
| 23-Jun-2013 |
tls | resync from head
|
| 1.35.14.1 |
| 25-Feb-2013 |
tls | resync with head
|
| 1.35.4.2 |
| 22-May-2014 |
yamt | sync with head.
for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.
this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")
|
| 1.35.4.1 |
| 23-Jan-2013 |
yamt | sync with head
|
| 1.37.10.2 |
| 28-Aug-2017 |
skrll | Sync with HEAD
|
| 1.37.10.1 |
| 06-Jun-2015 |
skrll | Sync with HEAD
|
| 1.37.8.1 |
| 04-Nov-2015 |
riz | Pull up following revision(s) (requested by riastradh in ticket #896):
sys/ufs/ffs/ffs_bswap.c: revision 1.38
sys/ufs/ffs/ffs_bswap.c: revision 1.39
Don't (harmlessly) overrun di_db array; copy di_ib separately.
Noted by Coverity, CID 974635.
While here, simplify size calculation for memcpy.
memcpy di_extb/db/ib separately. Noted by Coverity, CID 974636.
|
| 1.39.4.1 |
| 21-Apr-2017 |
bouyer | Sync with HEAD
|
| 1.39.2.1 |
| 20-Mar-2017 |
pgoyette | Sync with HEAD
|
