From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 209039] xfs_fsr skips most of the files as no improvement will be made
Date: Wed, 26 Aug 2020 16:27:43 +0000 [thread overview]
Message-ID: <bug-209039-201763-TSIe5cCFpr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209039-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209039
Eric Sandeen (sandeen@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #3 from Eric Sandeen (sandeen@redhat.com) ---
If you'd like to send a patch, go ahead; in general verbose+debugging messages
are going to be less user-friendly than normal rogram output; they are
inherently more for developer eyes vs. user eyes.
This might also get into messiness about how we assess four separate but
contiguous maximally-sized extents; is that 4 "extents" or one? I'd have to
dig into the xfs_fsr reporting to see how it's counting, but I'm not really
sure it's all worth the effort - fsr /is/ doing the right thing here.
In the end, the default verbose output is completely correct: "No improvement
will be made" - and it probably doesn't need any update.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-26 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 7:40 [Bug 209039] New: xfs_fsr skips most of the files as no improvement will be made bugzilla-daemon
2020-08-26 10:33 ` Brian Foster
2020-08-26 10:33 ` [Bug 209039] " bugzilla-daemon
2020-08-26 11:04 ` bugzilla-daemon
2020-08-26 16:27 ` bugzilla-daemon [this message]
2020-09-01 7:50 ` bugzilla-daemon
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=bug-209039-201763-TSIe5cCFpr@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).