This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations. (June 2011) (Learn how and when to remove this template message)

Soft updates is an approach to maintaining file system meta-data integrity in the event of a crash or power outage. Soft updates work by tracking and enforcing dependencies among updates to file system meta-data. Soft updates are an alternative to the more commonly used approach of journaling file systems.

Method of operation

Soft updates allow only asynchronous metadata writes that do not render the on-disk file system inconsistent, or that the only inconsistency that ever happens is a storage space leak (space marked allocated when not used by any file). It avoids having to do ordered synchronous metadata writes by temporarily "rolling back" any part of a metadata block that depends on another potentially non-flushed or partially rolled-back block when writing it.

In effect, blocks may be flushed at any time and the soft-update code will always provide the disk a consistent version of it (as long as it knows which blocks have physically been flushed). Recovery then simply becomes a matter of running a background walk of the file system when it is next mounted to garbage collect any allocated space that has been orphaned. This also permits the filesystem to selectively flush certain files without having to flush all metadata blocks or all of the records.

Data that is unlinked from the metadata dependency graph before writing it to disk has begun does not need to be written to disk at all. For example, creating a file, using it for a short period of time, and then deleting it may cause no disk activity at all.

Soft updates require periodic flushing of the metadata to nonvolatile storage.


FreeBSD supports soft updates for the UFS file system[1] and they have been enabled by default during installation for many years. Soft updates are manually enabled or disabled during file system creation with an option to the newfs command.[2] They can be disabled or enabled anytime thereafter with an option to the tunefs command.[3] FreeBSD 9.0 introduced a journaling supplement to soft updates for the purpose of eliminating a background fsck for garbage collection after a crash.[4][5] However, enabling journaling on a filesystem with soft updates disables the ability to make filesystem snapshots.[6] This may cause issues when filesystems are dumped with the -L option, as snapshots are used to guarantee filesystem coherency during the dump.

OpenBSD supports soft updates for the FFS file system. Soft updates are enabled when the file system is mounted by exercising an option to the mount command.[7]

NetBSD supported soft updates until the 6.0 release (2012) at which time it was deprecated in favor of WAPBL journaling.[8]

Comparison to journaling file systems

Neither journaling nor soft updates guarantees that no data will be lost, but they do make sure that the filesystem remains consistent.

An advantage of a file system with soft updates is that it can be mounted immediately after a crash, since there is no log replay.



  1. ^ McKusick, Marshall Kirk; Neville-Neil, George V. (2005). "8.6". The Design and Implementation of the FreeBSD Operating System. Addison-Wesley. ISBN 978-0321968975.
  2. ^ "newfs(8)". FreeBSD. 2017-07-07. Retrieved 2019-02-02.
  3. ^ "tunefs(8)". FreeBSD. 2016-04-19. Retrieved 2019-02-02.
  4. ^ "FreeBSD 9.0-RELEASE Release Notes". FreeBSD. 2012-01-12. Retrieved 2019-02-02.
  5. ^ McKusick, Marshall Kirk; Roberson, Jeff (2010-01-23). "Journaled Soft-updates" (PDF). Retrieved 2019-02-02.
  6. ^ "Bug 195485 - [ufs] mksnap_ffs(8) cannot create snapshot with journaled soft updates enabled". FreeBSD. 2014-11-28. Retrieved 2019-02-02.
  7. ^ "mount(8)". OpenBSD. 2018-01-18. Retrieved 2019-02-02.
  8. ^ "Announcing NetBSD 6.0". NetBSD. 2012-10-17. Retrieved 2019-02-02.