The Design and Implementation of the FreeBSD Operating System, Second Edition
Now available: The Design and Implementation of the FreeBSD Operating System (Second Edition)


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

FreeBSD/Linux Kernel Cross Reference
sys/ufs/ffs/README.softupdates

Version: -  FREEBSD  -  FREEBSD-13-STABLE  -  FREEBSD-13-0  -  FREEBSD-12-STABLE  -  FREEBSD-12-0  -  FREEBSD-11-STABLE  -  FREEBSD-11-0  -  FREEBSD-10-STABLE  -  FREEBSD-10-0  -  FREEBSD-9-STABLE  -  FREEBSD-9-0  -  FREEBSD-8-STABLE  -  FREEBSD-8-0  -  FREEBSD-7-STABLE  -  FREEBSD-7-0  -  FREEBSD-6-STABLE  -  FREEBSD-6-0  -  FREEBSD-5-STABLE  -  FREEBSD-5-0  -  FREEBSD-4-STABLE  -  FREEBSD-3-STABLE  -  FREEBSD22  -  l41  -  OPENBSD  -  linux-2.6  -  MK84  -  PLAN9  -  xnu-8792 
SearchContext: -  none  -  3  -  10 

    1 $FreeBSD: releng/5.2/sys/ufs/ffs/README.softupdates 62798 2000-07-08 02:31:21Z mckusick $
    2 
    3 Using Soft Updates
    4 
    5 To enable the soft updates feature in your kernel, add option
    6 SOFTUPDATES to your kernel configuration.
    7 
    8 Once you are running a kernel with soft update support, you need to enable
    9 it for whichever filesystems you wish to run with the soft update policy.
   10 This is done with the -n option to tunefs(8) on the UNMOUNTED filesystems,
   11 e.g. from single-user mode you'd do something like:
   12 
   13         tunefs -n enable /usr
   14 
   15 To permanently enable soft updates on the /usr filesystem (or at least
   16 until a corresponding ``tunefs -n disable'' is done).
   17 
   18 
   19 Soft Updates Copyright Restrictions
   20 
   21 As of June 2000 the restrictive copyright has been removed and 
   22 replaced with a `Berkeley-style' copyright. The files implementing
   23 soft updates now reside in the sys/ufs/ffs directory and are
   24 compiled into the generic kernel by default.
   25 
   26 
   27 Soft Updates Status
   28 
   29 The soft updates code has been running in production on many
   30 systems for the past two years generally quite successfully.
   31 The two current sets of shortcomings are:
   32 
   33 1) On filesystems that are chronically full, the two minute lag
   34    from the time a file is deleted until its free space shows up
   35    will result in premature filesystem full failures. This
   36    failure mode is most evident in small filesystems such as
   37    the root. For this reason, use of soft updates is not
   38    recommended on the root filesystem.
   39 
   40 2) If your system routines runs parallel processes each of which
   41    remove many files, the kernel memory rate limiting code may
   42    not be able to slow removal operations to a level sustainable
   43    by the disk subsystem. The result is that the kernel runs out
   44    of memory and hangs.
   45 
   46 Both of these problems are being addressed, but have not yet
   47 been resolved. There are no other known problems at this time.
   48 
   49 
   50 How Soft Updates Work
   51 
   52 For more general information on soft updates, please see:
   53         http://www.mckusick.com/softdep/
   54         http://www.ece.cmu.edu/~ganger/papers/CSE-TR-254-95/
   55 
   56 --
   57 Marshall Kirk McKusick <mckusick@mckusick.com>
   58 July 2000

Cache object: d1392ceebacc835f038287275a93528f


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]


This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.