public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: lukas@herbolt.com
To: djwong@kernel.org
Cc: linux-xfs@vger.kernel.org, Lukas Herbolt <lukas@herbolt.com>
Subject: [PATCH] xfsdocs: Small fix to correct first free inode to be 5847 not 5856.
Date: Thu, 25 Mar 2021 09:14:16 +0100	[thread overview]
Message-ID: <20210325081416.3190060-1-lukas@herbolt.com> (raw)
In-Reply-To: <20210324184835.GU22100@magnolia>

From: Lukas Herbolt <lukas@herbolt.com>

Thanks for confirmation, I was not sure about it.

Signed-off-by: Lukas Herbolt <lukas@herbolt.com>
---
 design/XFS_Filesystem_Structure/allocation_groups.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/design/XFS_Filesystem_Structure/allocation_groups.asciidoc b/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
index 992615d..cdc8545 100644
--- a/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
+++ b/design/XFS_Filesystem_Structure/allocation_groups.asciidoc
@@ -1099,7 +1099,7 @@ recs[1-85] = [startino,freecount,free]
 Most of the inode chunks on this filesystem are totally full, since the +free+
 value is zero.  This means that we ought to expect inode 160 to be linked
 somewhere in the directory structure.  However, notice that 0xff80000000000000
-in record 85 -- this means that we would expect inode 5856 to be free.  Moving
+in record 85 -- this means that we would expect inode 5847 to be free.  Moving
 on to the free inode B+tree, we see that this is indeed the case:
 
 ----
-- 
2.26.2


  reply	other threads:[~2021-03-25  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  8:34 xfs-docs question lukas
2021-03-24 18:48 ` Darrick J. Wong
2021-03-25  8:14   ` lukas [this message]
2021-03-26  2:42     ` [PATCH] xfsdocs: Small fix to correct first free inode to be 5847 not 5856 Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210325081416.3190060-1-lukas@herbolt.com \
    --to=lukas@herbolt.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox