[ceph-users] Re: Question about PR merge

2024-04-22 Thread Xiubo Li
Hi Nigel, For your issue I created a dedicated tracker, please see https://tracker.ceph.com/issues/65630. I have found the root cause and I am still trying to find the proper way to fix it. Please watch the tracker. Thanks - Xiubo On 4/18/24 14:22, Nigel Williams wrote: Hi Xiubo, Is

[ceph-users] Re: Question about PR merge

2024-04-18 Thread Xiubo Li
Hi Nigel, The logs you provide is totally a different issue, it's deadlock between two MDSs for a rename request. I will continue work on it today and tomorrow. While Erich's is mostly like the lock order issue as I mentioned in the previous mails, but still waiting the debug logs to

[ceph-users] Re: Question about PR merge

2024-04-18 Thread Nigel Williams
Hi Xiubo, Is the issue we provided logs on the same as Erich or is that a third different locking issue? thanks, nigel. On Thu, 18 Apr 2024 at 12:29, Xiubo Li wrote: > > On 4/18/24 08:57, Erich Weiler wrote: > >> Have you already shared information about this issue? Please do if not. > > > >

[ceph-users] Re: Question about PR merge

2024-04-17 Thread Xiubo Li
On 4/18/24 08:57, Erich Weiler wrote: Have you already shared information about this issue? Please do if not. I am working with Xiubo Li and providing debugging information - in progress! From the blocked ops output it very similiar the same issue as Patrick's lock order fixed before. I

[ceph-users] Re: Question about PR merge

2024-04-17 Thread Erich Weiler
Have you already shared information about this issue? Please do if not. I am working with Xiubo Li and providing debugging information - in progress! I was wondering if it would be included in 18.2.3 which I *think* should be released soon? Is there any way of knowing if that is true?

[ceph-users] Re: Question about PR merge

2024-04-17 Thread Patrick Donnelly
On Wed, Apr 17, 2024 at 11:36 AM Erich Weiler wrote: > > Hello, > > We are tracking PR #56805: > > https://github.com/ceph/ceph/pull/56805 > > And the resolution of this item would potentially fix a pervasive and > ongoing issue that needs daily attention in our cephfs cluster. Have you already