0b0c10b48d
description:
How it works:
--
Basically ifs is a copy of ffs, overriding some vfs/vnops. (Yes, hack.)
I didn't see the need in duplicating all of sys/ufs/ffs to get this
off the ground.
File creation is done through a special file - 'newfile' . When newfile
is called, the system allocates and returns an inode. Note that newfile
is done in a cloning fashion:
fd = open("newfile", O_CREAT|O_RDWR, 0644);
fstat(fd, &st);
printf("new file is %d\n", (int)st.st_ino);
Once you have created a file, you can open() and unlink() it by its returned
inode number retrieved from the stat call, ie:
fd = open("5", O_RDWR);
The creation permissions depend entirely if you have write access to the
root directory of the filesystem.
To get the list of currently allocated inodes, VOP_READDIR has been added
which returns a directory listing of those currently allocated.
--
What this entails:
* patching conf/files and conf/options to include IFS as a new compile
option (and since ifs depends upon FFS, include the FFS routines)
* An entry in i386/conf/NOTES indicating IFS exists and where to go for
an explanation
* Unstaticize a couple of routines in src/sys/ufs/ffs/ which the IFS
routines require (ffs_mount() and ffs_reload())
* a new bunch of routines in src/sys/ufs/ifs/ which implement the IFS
routines. IFS replaces some of the vfsops, and a handful of vnops -
most notably are VFS_VGET(), VOP_LOOKUP(), VOP_UNLINK() and VOP_READDIR().
Any other directory operation is marked as invalid.
What this results in:
* an IFS partition's create permissions are controlled by the perm/ownership of
the root mount point, just like a normal directory
* Each inode has perm and ownership too
* IFS does *NOT* mean an FFS partition can be opened per inode. This is a
completely seperate filesystem here
* Softupdates doesn't work with IFS, and really I don't think it needs it.
Besides, fsck's are FAST. (Try it :-)
* Inodes 0 and 1 aren't allocatable because they are special (dump/swap IIRC).
Inode 2 isn't allocatable since UFS/FFS locks all inodes in the system against
this particular inode, and unravelling THAT code isn't trivial. Therefore,
useful inodes start at 3.
Enjoy, and feedback is definitely appreciated!
|
||
|---|---|---|
| .. | ||
| ffs_alloc.c | ||
| ffs_balloc.c | ||
| ffs_extern.h | ||
| ffs_inode.c | ||
| ffs_snapshot.c | ||
| ffs_softdep_stub.c | ||
| ffs_softdep.c | ||
| ffs_subr.c | ||
| ffs_tables.c | ||
| ffs_vfsops.c | ||
| ffs_vnops.c | ||
| fs.h | ||
| README.snapshot | ||
| README.softupdates | ||
| softdep.h | ||
$FreeBSD$ Using Soft Updates To enable the soft updates feature in your kernel, add option SOFTUPDATES to your kernel configuration. Once you are running a kernel with soft update support, you need to enable it for whichever filesystems you wish to run with the soft update policy. This is done with the -n option to tunefs(8) on the UNMOUNTED filesystems, e.g. from single-user mode you'd do something like: tunefs -n enable /usr To permanently enable soft updates on the /usr filesystem (or at least until a corresponding ``tunefs -n disable'' is done). Soft Updates Copyright Restrictions As of June 2000 the restrictive copyright has been removed and replaced with a `Berkeley-style' copyright. The files implementing soft updates now reside in the sys/ufs/ffs directory and are compiled into the generic kernel by default. Soft Updates Status The soft updates code has been running in production on many systems for the past two years generally quite successfully. The two current sets of shortcomings are: 1) On filesystems that are chronically full, the two minute lag from the time a file is deleted until its free space shows up will result in premature filesystem full failures. This failure mode is most evident in small filesystems such as the root. For this reason, use of soft updates is not recommended on the root filesystem. 2) If your system routines runs parallel processes each of which remove many files, the kernel memory rate limiting code may not be able to slow removal operations to a level sustainable by the disk subsystem. The result is that the kernel runs out of memory and hangs. Both of these problems are being addressed, but have not yet been resolved. There are no other known problems at this time. How Soft Updates Work For more general information on soft updates, please see: http://www.mckusick.com/softdep/ http://www.ece.cmu.edu/~ganger/papers/CSE-TR-254-95/ -- Marshall Kirk McKusick <mckusick@mckusick.com> July 2000