From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/1] xfs_spaceman: report health problems
Date: Tue, 10 Sep 2019 09:28:33 +1000 [thread overview]
Message-ID: <20190909232833.GE16973@dread.disaster.area> (raw)
In-Reply-To: <156774079788.2643029.845208737705520807.stgit@magnolia>
On Thu, Sep 05, 2019 at 08:33:17PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Use the fs and ag geometry ioctls to report health problems to users.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> libfrog/fsgeom.c | 16 ++
> libfrog/fsgeom.h | 1
> man/man8/xfs_spaceman.8 | 28 +++
> spaceman/Makefile | 2
> spaceman/health.c | 459 +++++++++++++++++++++++++++++++++++++++++++++++
> spaceman/init.c | 1
> spaceman/space.h | 1
> 7 files changed, 507 insertions(+), 1 deletion(-)
> create mode 100644 spaceman/health.c
Looks good. Minor nit below, but otherwise:
Reviewed-by: Dave Chinner <dchinner@redhat.com>
> +static int
> +report_bulkstat_health(
> + xfs_agnumber_t agno)
> +{
> + struct xfs_bstat bstat[BULKSTAT_NR];
> + char descr[256];
> + uint64_t startino = 0;
> + uint64_t lastino = -1ULL;
> + uint32_t ocount;
> + uint32_t i;
> + int error;
> +
> + if (agno != NULLAGNUMBER) {
> + startino = cvt_agino_to_ino(&file->xfd, agno, 0);
> + lastino = cvt_agino_to_ino(&file->xfd, agno + 1, 0) - 1;
> + }
> +
> + while ((error = xfrog_bulkstat(&file->xfd, &startino, BULKSTAT_NR,
> + bstat, &ocount) == 0) && ocount > 0) {
> + for (i = 0; i < ocount; i++) {
> + if (bstat[i].bs_ino > lastino)
> + goto out;
> + snprintf(descr, sizeof(descr) - 1, _("inode %llu"),
> + bstat[i].bs_ino);
> + report_sick(descr, inode_flags, bstat[i].bs_sick,
> + bstat[i].bs_checked);
> + }
> + }
This could be done as a do { } while loop:
do {
error = xfrog_bulkstat(&file->xfd, &startino, BULKSTAT_NR,
bstat, &ocount);
if (error)
break;
for (i = 0; i < ocount; i++) {
[....]
}
} while (ocount > 0);
This could be done as a followup patch as it's not critical, just
a little bit of cleanup...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-09-09 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 3:33 [PATCH 0/1] xfsprogs: online health tracking support Darrick J. Wong
2019-09-06 3:33 ` [PATCH 1/1] xfs_spaceman: report health problems Darrick J. Wong
2019-09-09 23:28 ` Dave Chinner [this message]
2019-09-16 19:29 ` [PATCH v2 " Darrick J. Wong
2019-09-24 21:55 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2019-09-25 21:30 [PATCH 0/1] xfsprogs: online health tracking support Darrick J. Wong
2019-09-25 21:31 ` [PATCH 1/1] xfs_spaceman: report health problems Darrick J. Wong
2019-08-26 21:20 [PATCH 0/1] xfsprogs: online health tracking support Darrick J. Wong
2019-08-26 21:20 ` [PATCH 1/1] xfs_spaceman: report health problems Darrick J. Wong
2019-09-04 4:52 ` Dave Chinner
2019-09-04 14:51 ` 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=20190909232833.GE16973@dread.disaster.area \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).