Hi,
Richard Brittain (co-worker of mine) created a bug report (#134572) about this issue a few weeks ago. Until that sees some action, I'm wondering if anyone has ideas for a workaround. Essentially the problem is this. With the new 1.8 Linux client on Redhat 7.5, a user logs into a system with AFS homes and gets an error as part of the login process. For bash the error is: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory For tcsh I think it is: tcsh: No such file or directory tcsh: Trying to start from /afs/path/to/home Regardless, the user has a valid token and has normal access to their home directory but some applications generate the same error. Presumably it's apps that use getcwd since I can replicate it with a trivial C program using the getcwd system call. What's weird is that it is client specific and only affects a few specific directories and only on that client. In other words, user1 logging into machineA will always get the error. user2 logging into machineA never does. user1 logging into machineB never does either. A reboot fixed it but it is very difficult to schedule a reboot (or any interruption of AFS) on these systems. I have tried fs flush, fs flushvolume, and fs flushmount using an affected home directory as the path argument and there is no change. I am relying on user feedback for that but it's from a user I trust. At the next scheduled reboot we could go back to the 1.6 series where this issue was first reported (Nov/Dec 2017), and then fixed, but... well that kind of stinks. :-) Any ideas to fix it on a running system? Anything useful I could do to flesh out the bug report? Is the issue already well enough understood that we are just waiting for the next point release in the 1.8 series? - Bill -- William D. Hamblen Research Systems Engineer Research Computing, Dartmouth College
