On 8/21/25 6:13 AM, Alperen Aksu wrote:
> Fixed typo error in referring to the section's headline
> Fixed to correct spelling of "mapping"
>
> Signed-off-by: Alperen Aksu <aksulperen@xxxxxxxxx>
Reviewed-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> ---
> Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 ++--
> 1 file 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 e231d127cd40..b39b588bb995 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
In the PDF that I looked at, section 3.1.1 is
3.1.1. Duplicate-Key-Insert Problem
if it matters.
> 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
thanks.
--
~Randy
