Customer 'stale file handle' problem
Customer has multiple web and SSH application nodes that have git-data on NFS mounts. Under some scenario, the repository becomes unavailable on some nodes and then operations like
git clone return an error
./packed-refs: stale file handle.
In the particular case we saw on a call, two of six nodes reported this error on the same repository. We then went on one of the nodes, navigated to the repository, and ran
ls in the directory.
git clone then worked fine.
- What was it about navigating to the repo and/or
lsin that directory that 'refreshed' and allowed things to work? Why wouldn't a
git clonecause the same refresh that an
- What causes the stale handle?
- Is some process keeping