CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

Journaling file system

file system that keeps track of not yet committed changes in a data structure called a “journal” (usually a circular log); when a system crash or power failure occurs, such file systems can be recovered online faster with less corruption

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJul 23, 2026
Entity authorityQ579047
Source-derived summary

A journaling file system is a file system that keeps track of changes not yet committed to the file system's main part by recording the goal of such changes in a data structure known as a "journal", which is usually a circular log. In the event of a system crash or power failure, such file systems can be brought back online more quickly with a lower likelihood of becoming corrupted.

Depending on the actual implementation, a journaling file system may only keep track of stored metadata, resulting in improved performance at the expense of increased possibility for data corruption. Alternatively, a journaling file system may track both stored data and related metadata, while some implementations allow selectable behavior in this regard.

History

In 1990 IBM introduced JFS in AIX 3.1 as one of the first UNIX commercial filesystems that implemented journaling. The next year the idea was popularized in a widely cited paper on log-structured file systems.

This was subsequently implemented in Microsoft's Windows NT's NTFS filesystem in 1993, in Apple's HFS Plus filesystem in 1998, and in Linux's ext3 filesystem in 2001.

Rationale

Updating file systems to reflect changes to files and directories usually requires many separate write operations. This makes it possible for an interruption (like a power failure or system crash) between writes to leave data structures in an invalid intermediate state.

For example, deleting a file on a Unix file system involves three steps:

Removing its directory entry.

Editorial summary

This brief starts where responsible research should: with the source description of “Journaling file system” as file system that keeps track of not yet committed changes in a data structure called a “journal” (usually a circular log); when a system crash or power failure occurs, such file systems can be recovered online faster with less corruption. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA practical starting point whose main value is the path it opens into stronger specialist and primary sources. The current lead gives the account dated anchors—1990, 1993, 1998, 2001—that can be checked directly. The selected authority fields contribute no independent date. The account is most persuasive where Journaling, file and system can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the general reference register because the source frames it as file system that keeps track of not yet committed changes in a data structure called a “journal” (usually a circular log); when a system crash or power failure occurs, such file systems can be recovered online faster with less corruption. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jul 23, 2026. The linked authority identifier is Q579047. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1990, 1993, 1998 and 2001.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Journaling file system”, its source revision and the description used here.
  2. Expand the search: follow Journaling file system primary sources, Journaling file system archive and Journaling research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Journaling file system”?
  2. Which cited source is closest to the event, object or claim?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Journaling file system” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.