From: Ilya Dryomov <idryomov@gmail.com>
To: Robin Geuze <robin.geuze@nl.team.blue>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: All RBD IO stuck after flapping OSD's
Date: Tue, 29 Jun 2021 12:07:12 +0200 [thread overview]
Message-ID: <CAOi1vP-dT=1C2SqcMxAR1NWrcHUE1K-F6M1BpBWb7pVCDhS7Og@mail.gmail.com> (raw)
In-Reply-To: <2d37c87eb42d4bc2a99184f6bffce8a2@nl.team.blue>
On Tue, Jun 29, 2021 at 10:39 AM Robin Geuze <robin.geuze@nl.team.blue> wrote:
>
> Hey Ilya,
>
> Do you have any idea on the cause of this bug yet? I tried to dig around a bit myself in the source, but the logic around this locking is very complex, so I couldn't figure out where the problem is.
I do. The proper fix would indeed be large and not backportable but
I have a workaround in mind that should be simple enough to backport
all the way to 5.4. The trick is making sure that the workaround is
fine from the exclusive lock protocol POV.
I'll try to flesh it out by the end of this week and report back
early next week.
Thanks,
Ilya
next prev parent reply other threads:[~2021-06-29 10:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 8:51 All RBD IO stuck after flapping OSD's Robin Geuze
2021-04-14 17:00 ` Ilya Dryomov
[not found] ` <8eb12c996e404870803e9a7c77e508d6@nl.team.blue>
2021-04-19 12:40 ` Ilya Dryomov
2021-06-16 11:56 ` Robin Geuze
2021-06-17 8:36 ` Ilya Dryomov
2021-06-17 8:42 ` Robin Geuze
2021-06-17 9:40 ` Ilya Dryomov
2021-06-17 10:17 ` Robin Geuze
2021-06-17 11:09 ` Ilya Dryomov
2021-06-17 11:12 ` Robin Geuze
2021-06-29 8:39 ` Robin Geuze
2021-06-29 10:07 ` Ilya Dryomov [this message]
2021-07-06 17:21 ` Ilya Dryomov
2021-07-07 7:35 ` Robin Geuze
2021-07-20 12:04 ` Robin Geuze
2021-07-20 16:42 ` Ilya Dryomov
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='CAOi1vP-dT=1C2SqcMxAR1NWrcHUE1K-F6M1BpBWb7pVCDhS7Og@mail.gmail.com' \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=robin.geuze@nl.team.blue \
/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).