-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to git clone on top of NFS share with Ganesha v6. #1132
Comments
you need ask SaunaFS community. |
Thank you for your answer @xiaods. I'm one of the maintainers of the SaunaFS community and as I said in my first comment, |
A working (4.3) and a non-working (6) tcp trace would help. I can't think of any permission processing changes, so not sure what it might be. Are you using the latest, V6-dev.14? |
Hi @ffilz, Thank you for your answer. At the moment of creating the issue, Below I share tcp traces generated with tcpdump for working (V4.3) and non-working (V6-dev.14) versions. Please, confirm whether this is what you need or if you need some other logs/traces. ganesha-v4.3 Thank you in advance, |
Hmm, the traces have no NFS traffic in them... |
Hi @ffilz, Sorry for being absent during the last days. I updated TCP traces to include NFS traces and also added the log generated when running the tests with each Ganesha version. I modified my previous comment to update the new information. Please, let me know if the new information is correct. Thanks for your support, |
I started having issues with one of the SaunaFS integration tests for Ganesha after updating our current SaunaFS FSAL (Compatible with Ganesha v4.3) with the version of SaunaFS FSAL released at the Ganesha repository (Compatible with Ganesha v6).
The failing test is the cthon test, that runs basically in two steps:
Previously, this test passed successfully. However, after upgrading, the git clone command fails with permission denied. If I run the git clone command on top of the SaunaFS mount, then the git clone works as expected and the test passes successfully.
I'm using this configuration file for the test:
The most important steps in the test are below:
The log produced during the test is the following: cthon.log
Did somebody have this issue? Any ideas about how to solve it?
Thanks in advance,
The text was updated successfully, but these errors were encountered: