freebsd

mirror of https://git.FreeBSD.org/src.git synced 2024-12-22 11:17:19 +00:00

History

Alexander Kabaev c355fd5a84 Avoid doing bawrite to initialize inode block while holding cylinder group block locked. If filesystem has any active snapshots, bawrite can come back trying to allocate new snapshot data block from the same cylinder group and cause panic due to recursive lock attempt. PR: 64206 Reviewed by: mckusick Tested by: pjd		2004-03-16 22:06:32 +00:00
..
ffs_alloc.c	Avoid doing bawrite to initialize inode block while holding cylinder	2004-03-16 22:06:32 +00:00
ffs_balloc.c
ffs_extern.h
ffs_inode.c
ffs_rawread.c
ffs_snapshot.c	Fix style bugs in previous commit.	2004-02-13 02:02:06 +00:00
ffs_softdep_stub.c
ffs_softdep.c	When I was a kid my work table was one cluttered mess an cleaning it up	2004-03-11 18:50:33 +00:00
ffs_subr.c
ffs_tables.c
ffs_vfsops.c	Fixed some style bugs:	2004-02-14 04:41:13 +00:00
ffs_vnops.c	Removed more vestiges of vfs_ioopt:	2004-02-11 15:27:26 +00:00
fs.h
README.snapshot
README.softupdates
softdep.h

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