diff options
| author | Alperen Aksu <aksulperen@gmail.com> | 2025-08-21 13:13:47 +0000 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2025-08-29 16:11:19 -0600 |
| commit | ba653158f40deccb3f79005bf1d5c6c37d45b247 (patch) | |
| tree | 2b1ee1fbee2a3a278044fe5929552d6ffa0886bb | |
| parent | c67a9f492c3c15ef1695c629bf5cc57f674a8e83 (diff) | |
| download | tip-ba653158f40deccb3f79005bf1d5c6c37d45b247.tar.gz | |
Documentation/filesystems/xfs: Fix typo error
Fixed typo error in referring to the section's headline
Fixed to correct spelling of "mapping"
Signed-off-by: Alperen Aksu <aksulperen@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250821131404.25461-1-aksulperen@gmail.com
| -rw-r--r-- | Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst index 9fe99435339584..8cbcd3c2643430 100644 --- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst +++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst @@ -475,7 +475,7 @@ operation, which may cause application failure or an unplanned filesystem shutdown. Inspiration for the secondary metadata repair strategy was drawn from section -2.4 of Srinivasan above, and sections 2 ("NSF: Inded Build Without Side-File") +2.4 of Srinivasan above, and sections 2 ("NSF: Index Build Without Side-File") and 3.1.1 ("Duplicate Key Insert Problem") in C. Mohan, `"Algorithms for Creating Indexes for Very Large Tables Without Quiescing Updates" <https://dl.acm.org/doi/10.1145/130283.130337>`_, 1992. @@ -4179,7 +4179,7 @@ When the exchange is initiated, the sequence of operations is as follows: This will be discussed in more detail in subsequent sections. If the filesystem goes down in the middle of an operation, log recovery will -find the most recent unfinished maping exchange log intent item and restart +find the most recent unfinished mapping exchange log intent item and restart from there. This is how atomic file mapping exchanges guarantees that an outside observer will either see the old broken structure or the new one, and never a mismash of |