Derek Su

Hello @mantissahz Is the PR ready?

@mantissahz Ready to review?

Hello @proligde, We've identified the issue in https://github.com/longhorn/longhorn/issues/8394, and the fix will be included in the upcoming v1.6.2. Before v1.6.2, you can try the [workaround](https://github.com/longhorn/longhorn/issues/8394#issuecomment-2069398514). Thank you.

>  > > ``` > top - 03:27:43 up 14 days, 19 min, 0 users, load average: 0.16, 0.28, 0.64 > Tasks: 9 total, 1 running, 8 sleeping, 0...

@wangwill Can you provide a support bundle for further analysis and steps to reproduce it? Thank you.

@wangwill You can generate a support bundle by https://longhorn.io/docs/1.6.2/troubleshoot/support-bundle/ and send it to [email protected]. In addition, please provide the steps to reproduce the memory leak issue. Thank you.

Thank you, @james-munson. Can you cherry-pick the https://github.com/nfs-ganesha/nfs-ganesha/commit/60e582ce6d0217458f49384491aaacb3815f14a3 to our codes and prepare a customized image for testing?

@james-munson Do you know which commit in nfs-ganesha results in the leak?

> I have this issue in 1.7.0. How can I help to investigate/solve? @klucsik Didn't see it in v1.6.x?

@klucsik It sounds not related to the issue. Could you create a new ticket with more information such as cluster info, host info, support bundle with the issue you mentioned...