Skip to content
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

Open
ralcolea opened this issue May 11, 2024 · 5 comments
Open

Unable to git clone on top of NFS share with Ganesha v6. #1132

ralcolea opened this issue May 11, 2024 · 5 comments
Labels
Analyzing Need Info Need more information from the reporter

Comments

@ralcolea
Copy link
Contributor

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:

  1. Clone and build cthon repository on top of the NFS share exported with Ganesha: FAILED
  2. Run cthon tests for NFS share: SUCCESS

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:

NFSV4 {
	Grace_Period = 5;
}
EXPORT
{
	Attr_Expiration_Time = 0;
	Export_Id = 99;
	Path = /data;
	Pseudo = /data;
	Access_Type = RW;
	FSAL {
		Name = SaunaFS;
		hostname = localhost;
		port = ${saunafs_info_[matocl]};
		# How often to retry to connect
		io_retries = 5;
		cache_expiration_time_ms = 2500;
	}
	Protocols = 4;
	CLIENT {
		Clients = localhost;
	}
}
LOG {
	COMPONENTS {
		NFSPROTO=FULL_DEBUG;
		NFS_V4=FULL_DEBUG;
		FSAL=FULL_DEBUG;
		EXPORT=FULL_DEBUG;
		NFS_V4_ACL=FULL_DEBUG;
	}
}

The most important steps in the test are below:

mkdir -p ${TEMP_DIR}/mnt/ganesha
mkdir -p ${info[mount0]}/data

sudo /usr/bin/ganesha.nfsd -f ${info[mount0]}/ganesha.conf -L /tmp/cthon.log
assert_eventually 'showmount -e localhost'

sudo mount -vvvv localhost:/data $TEMP_DIR/mnt/ganesha

# Run connectathon nfs suite
cd $TEMP_DIR/mnt/ganesha

mkdir cthon_tests
export NFSTESTDIR=$TEMP_DIR/mnt/ganesha/cthon_tests

git clone https://github.com/leil-io/cthon04.git # This is the failing step
cd cthon04
make all

./runtests -b -n
./runtests -l -n
./runtests -s -n

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,

@xiaods
Copy link

xiaods commented Jun 17, 2024

you need ask SaunaFS community.

@ralcolea
Copy link
Contributor Author

Thank you for your answer @xiaods.

I'm one of the maintainers of the SaunaFS community and as I said in my first comment, git clone works well with Ganesha v4.3, the version we currently support. However, after migrating our SaunaFS FSAL to v6, git clone stopped working due to permission issues. We didn't do changes in our FSAL, that's why I'm a little confused about what could be the cause of this issue.

@ffilz
Copy link
Member

ffilz commented Jun 19, 2024

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?

@ffilz ffilz added Analyzing Need Info Need more information from the reporter labels Jun 19, 2024
@ralcolea
Copy link
Contributor Author

Hi @ffilz,

Thank you for your answer.

At the moment of creating the issue, V6-dev.11 was the latest version available. However, I updated to V6-dev.14 and I have the same 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-v6-dev.14-issue-1132.zip
ganesha-v4.3-issue-1132.zip

Thank you in advance,

@ffilz
Copy link
Member

ffilz commented Jun 25, 2024

Hmm, the traces have no NFS traffic in them...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Analyzing Need Info Need more information from the reporter
Projects
None yet
Development

No branches or pull requests

3 participants