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

opal_path_nfs test fails with (timed-out) autofs mount #10152

Open
gkatev opened this issue Mar 22, 2022 · 0 comments
Open

opal_path_nfs test fails with (timed-out) autofs mount #10152

gkatev opened this issue Mar 22, 2022 · 0 comments

Comments

@gkatev
Copy link
Contributor

gkatev commented Mar 22, 2022

Hi, I'm encountering a failure with the tests/util/opal_path_nfs test. If I'm interpreting everything correctly, it looks like it is the test that is problematic and not opal_path_nfs().

Cherry-picking a specific mount from the list for demontration purposes:

$ ./opal_path_nfs 
...
get_mounts: dirs[48]:/p/arch fs:autofs nfs:No
...
test(): file:/p/arch bool:0
 Failure : Mismatch: input "/p/arch", expected:0 got:1
...

From what I can tell this filesystem indeed is nfs (mounted via autofs).

$ mount | grep /p/arch
/etc/auto.deep on /p/arch type autofs (...)

$ grep /p/arch /etc/mtab
/etc/auto.deep /p/arch autofs ...

$ grep /p/arch /etc/auto.deep
/p/arch			-rw	   <IP addr>:/arch/.

$ nfsstat -m | grep /p/arch
/p/arch from <IP addr>:/arch

Actually, when all offending mounts have been recently accessed, the test does succeed! When I can no longer see them in nfsstat -m, it is then that the test fails.

When the test is successful, I see something like:

get_mounts: dirs[48]:/p/arch fs:autofs nfs:No
...
get_mounts: already know dir[48]:/p/arch
get_mounts: dirs[48]:/p/arch fs:nfs4 nfs:Yes
...
test(): file:/p/arch bool:1

When it is not successful, only the first part, and not the "already know" part appers in the output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant