freebsd

mirror of https://git.FreeBSD.org/src.git synced 2024-12-19 10:53:58 +00:00

History

Robert Watson 7df97b6117 o At some point, unmounting a non-EA file system with EA's compiled in got a bit broken, when ufs_extattr_stop() was called and failed, ufs_extattr_destroy() would panic. This makes the call to destroy() conditional on the success of stop(). Submitted by: Christian Carstensen <cc@devcon.net> Obtained from: TrustedBSD Project		2001-09-01 20:11:05 +00:00
..
ffs_alloc.c	Fix warning:	2001-06-15 07:44:39 +00:00
ffs_balloc.c	VOP_BALLOC was never really a VOP in the first place, so convert it	2001-04-29 12:36:52 +00:00
ffs_extern.h	Forward declare struct cg to quiet a warning.	2001-05-30 23:08:40 +00:00
ffs_inode.c	When running with soft updates, track the number of blocks and files	2001-05-08 07:42:20 +00:00
ffs_snapshot.c	Further fixes for deadlock in the presence of multiple snapshots.	2001-05-14 17:16:49 +00:00
ffs_softdep_stub.c	Revert the previous commit in favor of the fix in rev 1.42 of	2001-05-30 23:09:19 +00:00
ffs_softdep.c	Build on the change in revision 1.98 by Tor.Egge@fast.no.	2001-06-13 23:13:13 +00:00
ffs_subr.c	Remove blatantly pointless call to VOP_BMAP().	2001-05-01 09:12:31 +00:00
ffs_tables.c	$Id$ -> $FreeBSD$	1999-08-28 01:08:13 +00:00
ffs_vfsops.c	o At some point, unmounting a non-EA file system with EA's compiled	2001-09-01 20:11:05 +00:00
ffs_vnops.c	Implement vop_std{get\|put}pages() and add them to the default vop[].	2001-05-01 08:34:45 +00:00
fs.h	Use a fixed type for times in on-disk structures for ufs rather than	2001-07-16 00:55:27 +00:00
README.snapshot	Update to describe use of mdconfig instead of deprecated vnconfig.	2001-04-14 18:32:09 +00:00
README.softupdates	Update to reflect current status.	2000-07-08 02:31:21 +00:00
softdep.h	When a new block is allocated to a directory, an fsync of a file	2001-05-17 07:24:03 +00:00

README.softupdates

$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