From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/5] xfs_repair: don't spray correcting imap all by itself
Date: Tue, 6 Jun 2023 12:50:49 +0200 [thread overview]
Message-ID: <20230606105049.ci2lrb72hlpegxun@andromeda> (raw)
In-Reply-To: <168597945921.1226461.946607316221373794.stgit@frogsfrogsfrogs>
On Mon, Jun 05, 2023 at 08:37:39AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> In xfs/155, I occasionally see this in the xfs_repair output:
>
> correcting imap
> correcting imap
> correcting imap
> ...
>
> This is completely useless, since we don't actually log which inode
> prompted this message. This logic has been here for a really long time,
> but ... I can't make heads nor tails of it. If we're running in verbose
> or dry-run mode, then print the inode number, but not if we're running
> in fixit mode?
>
> A few lines later, if we're running in verbose dry-run mode, we print
> "correcting imap" even though we're not going to write anything.
>
> If we get here, the inode looks like it's in use, but the inode index
> says it isn't. This is a corruption, so either we fix it or we say that
> we would fix it.
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
>
> Fixes: 6c39a3cbda3 ("Don't trash lost+found in phase 4 Merge of master-melb:xfs-cmds:29144a by kenmcd.")
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> repair/dino_chunks.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
>
> diff --git a/repair/dino_chunks.c b/repair/dino_chunks.c
> index cf6a5e399d4..33008853789 100644
> --- a/repair/dino_chunks.c
> +++ b/repair/dino_chunks.c
> @@ -871,13 +871,11 @@ process_inode_chunk(
> */
> if (is_used) {
> if (is_inode_free(ino_rec, irec_offset)) {
> - if (verbose || no_modify) {
> - do_warn(
> + do_warn(
> _("imap claims in-use inode %" PRIu64 " is free, "),
> ino);
> - }
>
> - if (verbose || !no_modify)
> + if (!no_modify)
> do_warn(_("correcting imap\n"));
> else
> do_warn(_("would correct imap\n"));
>
next prev parent reply other threads:[~2023-06-06 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 15:37 [PATCHSET 0/5] xfs_repair: fix corruption messaging with verbose mode Darrick J. Wong
2023-06-05 15:37 ` [PATCH 1/5] xfs_repair: don't spray correcting imap all by itself Darrick J. Wong
2023-06-06 10:50 ` Carlos Maiolino [this message]
2023-06-05 15:37 ` [PATCH 2/5] xfs_repair: don't log inode problems without printing resolution Darrick J. Wong
2023-06-06 10:56 ` Carlos Maiolino
2023-06-05 15:37 ` [PATCH 3/5] xfs_repair: fix messaging when shortform_dir2_junk is called Darrick J. Wong
2023-06-06 10:57 ` Carlos Maiolino
2023-06-05 15:37 ` [PATCH 4/5] xfs_repair: fix messaging in longform_dir2_entry_check_data Darrick J. Wong
2023-06-06 10:59 ` Carlos Maiolino
2023-06-05 15:38 ` [PATCH 5/5] xfs_repair: fix messaging when fixing imap due to sparse cluster Darrick J. Wong
2023-06-06 11:00 ` Carlos Maiolino
2023-06-05 18:59 ` [PATCHSET 0/5] xfs_repair: fix corruption messaging with verbose mode Pavel Reichl
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=20230606105049.ci2lrb72hlpegxun@andromeda \
--to=cem@kernel.org \
--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