Soft updates is an approach to maintainingfile systemmetadata integrity in the event of a crash or power outage. Soft updates work by tracking and enforcing dependencies among updates to file system metadata. Soft updates are an alternative to the more commonly used approach ofjournaling file systems.
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 updates code will always provide the disk a consistent version of the metadata (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 togarbage collect any allocated space that has been orphaned. This also permits the file system 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 theUFS 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 thenewfs command.[2] They can be disabled or enabled anytime thereafter with an option to thetunefs command.[3] FreeBSD 9.0 introduced a journaling supplement to soft updates for the purpose of eliminating a backgroundfsck for garbage collection after a crash.[4][5]
OpenBSD supported soft updates for the FFS file system until the release 7.4 (2023), at which time it was disabled.[6]
NetBSD supported soft updates until the 6.0 release (2012) at which time it was deprecated in favor ofWAPBL journaling.[7]
Neither journaling nor soft updates guarantees that no data will be lost, but they do make sure that the file system 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.