From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH RESEND] gfs2: Return more useful errors from gfs2_rgrp_send_discards()
Date: Tue, 17 May 2022 13:30:30 +0200 [thread overview]
Message-ID: <CAHc6FU5MgeJJfqvfkRau3ccEpfT0iLE3FGk9Md4dhrA2nZH5Gw@mail.gmail.com> (raw)
In-Reply-To: <5488b93e-96c8-9007-9ee4-667247fa8c30@redhat.com>
On Mon, May 9, 2022 at 12:41 PM Andrew Price <anprice@redhat.com> wrote:
> On 29/04/2022 15:08, Andrew Price wrote:
> > On 19/04/2022 16:49, Andrew Price wrote:
> >> On 05/04/2022 13:08, Andrew Price wrote:
> >>> The bug that 27ca8273f ("gfs2: Make sure FITRIM minlen is rounded up to
> >>> fs block size") fixes was a little confusing as the user saw
> >>> "Input/output error" which masked the -EINVAL that sb_issue_discard()
> >>> returned.
> >>>
> >>> sb_issue_discard() can fail for various reasons, so we should return its
> >>> return value from gfs2_rgrp_send_discards() to avoid all errors being
> >>> reported as IO errors.
> >>>
> >>> This improves error reporting for FITRIM and makes no difference to the
> >>> -o discard code path because the return value from
> >>> gfs2_rgrp_send_discards() gets thrown away in that case (and the option
> >>> switches off). Presumably that's why it was ok to just return -EIO in
> >>> the past, before FITRIM was implemented.
> >>>
> >>> Tested with xfstests.
> >>
> >> Can I get a thumbs-up or thumbs-down for this patch? It's pretty
> >> straightforward. I just don't want it to get forgotten about.
> >>
> >> Cheers,
> >> Andy
> >
> > Please could you take this patch?
> >
> > Cheers,
> > Andy
>
> For convenience, I've pushed this patch to gitlab:
>
> git fetch https://gitlab.com/andyprice/linux.git discard_errors
> git show FETCH_HEAD
Pulled, thanks.
Andreas
prev parent reply other threads:[~2022-05-17 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 12:08 [Cluster-devel] [PATCH RESEND] gfs2: Return more useful errors from gfs2_rgrp_send_discards() Andrew Price
2022-04-19 15:49 ` Andrew Price
2022-04-29 14:08 ` Andrew Price
2022-05-09 10:41 ` Andrew Price
2022-05-17 11:30 ` Andreas Gruenbacher [this message]
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=CAHc6FU5MgeJJfqvfkRau3ccEpfT0iLE3FGk9Md4dhrA2nZH5Gw@mail.gmail.com \
--to=agruenba@redhat.com \
/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).