From: cem@kernel.org
To: aalbersh@redhat.com
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: [PATCH v3 2/2] fsr: always print error messages from xfrog_defragrange()
Date: Tue, 31 Mar 2026 14:26:31 +0200 [thread overview]
Message-ID: <20260331122639.100956-3-cem@kernel.org> (raw)
In-Reply-To: <20260331122639.100956-1-cem@kernel.org>
From: Carlos Maiolino <cem@kernel.org>
Error messages from xfrog_defragrange() are only printed when
verbose/debug flags are used.
We had reports from users complaining it's hard to find out the error
messages lost in the middle of dozens of other informational messages.
Change packfile() behavior to print errors independently of verbose or
debug flags.
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
---
V3: Rebase on top of patch 1 changes
V2: Update commit description
fsr/xfs_fsr.c | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/fsr/xfs_fsr.c b/fsr/xfs_fsr.c
index 390f7c5276df..24617f55e329 100644
--- a/fsr/xfs_fsr.c
+++ b/fsr/xfs_fsr.c
@@ -1464,19 +1464,14 @@ packfile(
case 0:
break;
case ENOTSUP:
- if (vflag || dflag)
- fsrprintf(_("%s: file type not supported\n"), fname);
break;
case EFAULT:
/* The file has changed since we started the copy */
- if (vflag || dflag)
- fsrprintf(_("%s: file modified defrag aborted\n"),
- fname);
+ fsrprintf(_("%s: file modified defrag aborted\n"), fname);
break;
case EBUSY:
/* Timestamp has changed or mmap'ed file */
- if (vflag || dflag)
- fsrprintf(_("%s: file busy\n"), fname);
+ fsrprintf(_("%s: file busy\n"), fname);
break;
default:
fsrprintf(_("XFS_IOC_SWAPEXT failed: %s: %s\n"),
--
2.53.0
next prev parent reply other threads:[~2026-03-31 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 12:26 [PATCH v3 0/2] Improve user experience with xfs_fsr cem
2026-03-31 12:26 ` [PATCH v3 1/2] fsr: package function should check for negative errors cem
2026-03-31 16:08 ` Darrick J. Wong
2026-03-31 12:26 ` cem [this message]
2026-03-31 16:09 ` [PATCH v3 2/2] fsr: always print error messages from xfrog_defragrange() 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=20260331122639.100956-3-cem@kernel.org \
--to=cem@kernel.org \
--cc=aalbersh@redhat.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