From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/5] xfs_scrub: report repair activities on stdout, not stderr
Date: Fri, 1 Nov 2019 11:42:29 -0700 [thread overview]
Message-ID: <20191101184229.GZ15222@magnolia> (raw)
In-Reply-To: <ff4b4193-c6e1-130f-7e09-f8bb9790c33a@sandeen.net>
On Fri, Nov 01, 2019 at 01:26:49PM -0500, Eric Sandeen wrote:
> On 10/22/19 1:46 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Reduce the severity of reports about successful metadata repairs. We
> > fixed the problem, so there's no action necessary on the part of the
> > system admin.
>
> Hm, ok. "we found corruption" seems quite important, but I guess it's
> not an operational error of the utility. *shrug*
We *fixed* corruption, meaning that the fs is ok now.
If we left corruption behind (either because the user gave us "-n" or
the repair failed) then we still yell about it on stderr.
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > scrub/common.c | 2 +-
> > scrub/common.h | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> >
> > diff --git a/scrub/common.c b/scrub/common.c
> > index b41f443d..7632a8d8 100644
> > --- a/scrub/common.c
> > +++ b/scrub/common.c
> > @@ -48,7 +48,7 @@ static struct {
> > } err_levels[] = {
> > [S_ERROR] = { .string = "Error", .loglevel = LOG_ERR },
> > [S_WARN] = { .string = "Warning", .loglevel = LOG_WARNING },
> > - [S_REPAIR] = { .string = "Repaired", .loglevel = LOG_WARNING },
> > + [S_REPAIR] = { .string = "Repaired", .loglevel = LOG_INFO },
> > [S_INFO] = { .string = "Info", .loglevel = LOG_INFO },
> > [S_PREEN] = { .string = "Optimized", .loglevel = LOG_INFO }
>
> My OCD wants this in the same order as error_level, I'll change that
> on commit if it's ok w/ you. And if I remember.
<nod>
--D
> Reviewed-by: Eric Sandeen <sandeen@redhat.com>
>
> > };
> > diff --git a/scrub/common.h b/scrub/common.h
> > index 9a37e9ed..ef4cf439 100644
> > --- a/scrub/common.h
> > +++ b/scrub/common.h
> > @@ -18,8 +18,8 @@ bool xfs_scrub_excessive_errors(struct scrub_ctx *ctx);
> > enum error_level {
> > S_ERROR = 0,
> > S_WARN,
> > - S_REPAIR,
> > S_INFO,
> > + S_REPAIR,
> > S_PREEN,
> > };
> >
> >
next prev parent reply other threads:[~2019-11-01 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 18:46 [PATCH 0/5] xfsprogs: random fixes Darrick J. Wong
2019-10-22 18:46 ` [PATCH 1/5] xfs_spaceman: always report sick metadata, checked or not Darrick J. Wong
2019-11-01 18:17 ` Eric Sandeen
2019-11-01 18:40 ` Darrick J. Wong
2019-11-01 18:44 ` Darrick J. Wong
2019-10-22 18:46 ` [PATCH 2/5] xfs_db: btheight should check geometry more carefully Darrick J. Wong
2019-11-01 18:21 ` Eric Sandeen
2019-10-22 18:46 ` [PATCH 3/5] xfs_scrub: report repair activities on stdout, not stderr Darrick J. Wong
2019-11-01 18:26 ` Eric Sandeen
2019-11-01 18:42 ` Darrick J. Wong [this message]
2019-10-22 18:46 ` [PATCH 4/5] xfs_scrub: don't allow error or negative error injection interval Darrick J. Wong
2019-11-01 18:31 ` Eric Sandeen
2019-10-22 18:47 ` [PATCH 5/5] libfrog: fix workqueue_add error out Darrick J. Wong
2019-11-01 18:33 ` Eric Sandeen
2019-10-30 17:52 ` [PATCH 6/5] xfs_repair: print better information when metadata updates fail Darrick J. Wong
2019-11-01 18:42 ` Eric Sandeen
2019-10-30 17:53 ` [PATCH 7/5] libxfs: fix typo in message about write verifier Darrick J. Wong
2019-11-01 18:44 ` Eric Sandeen
2019-11-01 18:52 ` [PATCH 8/5] mkfs: fix incorrect error message Darrick J. Wong
2019-11-01 19:28 ` Eric Sandeen
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=20191101184229.GZ15222@magnolia \
--to=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).