Linux XFS filesystem development
 help / color / mirror / Atom feed
From: bodonnel@redhat.com
To: linux-xfs@vger.kernel.org
Cc: sandeen@sandeen.net, djwong@kernel.org,
	Bill O'Donnell <bodonnel@redhat.com>
Subject: [PATCH v2] xfs_repair: fix link counts update following repair of a bad block
Date: Tue, 15 Apr 2025 10:01:04 -0500	[thread overview]
Message-ID: <20250415150103.63316-2-bodonnel@redhat.com> (raw)

From: Bill O'Donnell <bodonnel@redhat.com>

Updating nlinks, following repair of a bad block needs a bit of work.
In unique cases, 2 runs of xfs_repair is needed to adjust the count to
the proper value. This patch modifies location of longform_dir2_entry_check,
moving longform_dir2_entry_check_data to run after the check_dir3_header
error check. This results in the hashtab to be correctly filled and those
entries don't end up in lost+found, and nlinks is properly adjusted on the
first xfs_repair pass.

Suggested-by: Eric Sandeen <sandeen@sandeen.net>

Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
---
v2: add logic to cover shortform directory.


 repair/phase6.c | 20 +++++++++++++++++---
 1 file changed, 17 insertions(+), 3 deletions(-)

diff --git a/repair/phase6.c b/repair/phase6.c
index dbc090a54139..8fc1c3896d2b 100644
--- a/repair/phase6.c
+++ b/repair/phase6.c
@@ -2426,6 +2426,23 @@ longform_dir2_entry_check(
 
 		/* check v5 metadata */
 		if (xfs_has_crc(mp)) {
+			longform_dir2_entry_check_data(mp, ip, num_illegal,
+				need_dot,
+				irec, ino_offset, bp, hashtab,
+				&freetab, da_bno, fmt == XFS_DIR2_FMT_BLOCK);
+			error = check_dir3_header(mp, bp, ino);
+			if (error) {
+				fixit++;
+				if (fmt == XFS_DIR2_FMT_BLOCK)
+					goto out_fix;
+
+				libxfs_buf_relse(bp);
+				bp = NULL;
+				continue;
+			}
+		}
+		else {
+			/* No crc. Directory appears to be shortform. */
 			error = check_dir3_header(mp, bp, ino);
 			if (error) {
 				fixit++;
@@ -2438,9 +2455,6 @@ longform_dir2_entry_check(
 			}
 		}
 
-		longform_dir2_entry_check_data(mp, ip, num_illegal, need_dot,
-				irec, ino_offset, bp, hashtab,
-				&freetab, da_bno, fmt == XFS_DIR2_FMT_BLOCK);
 		if (fmt == XFS_DIR2_FMT_BLOCK)
 			break;
 
-- 
2.49.0


             reply	other threads:[~2025-04-15 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 15:01 bodonnel [this message]
2025-04-15 17:07 ` [PATCH v2] xfs_repair: fix link counts update following repair of a bad block Darrick J. Wong
2025-04-15 17:17   ` Bill O'Donnell

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=20250415150103.63316-2-bodonnel@redhat.com \
    --to=bodonnel@redhat.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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