[BUG] Bash tool hangs indefinitely (~25s timeout) when working directory is on NFS mount
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Version: 2.1.68 (native installer, Bun runtime)
OS: Linux (HPC cluster, RHEL 9 — kernel 5.14.0-570.58.1.el9_6.x86_64)
Description:
When Claude Code is launched from an NFS-mounted working directory, the Bash tool appears to hang silently — no output is produced, no permission prompt appears, and the command
eventually times out (~25s). The tool shows "running" status throughout.
Environment:
- Working directory: NFS mount (/nfs/hpc/share/user_name/dir_name/dir_name)
- Home directory: also NFS (/nfs/stak/users/user_name/)
- settings.json: {"skipDangerousModePermissionPrompt": true}
What was ruled out:
- Slow shell initialization — ruled out by testing
- Permission prompt accidentally dismissed — no prompt appears at all
- Network connectivity — other tools (Read, Glob, Grep, Write) all work correctly
Comparison:
Cursor Agent on the same machine and same directory executes shell commands with no issues.
Additional context from debug logs (~/.claude/debug/):
The earlier session (68528c6a) shows an OOM error during a self-update download, suggesting Bun may have memory constraints on this system that could also affect subprocess
spawning.
What Should Happen?
Claude should be able to execute bash commands with no problem
Error Messages/Logs
Steps to Reproduce
- Launch claude from an NFS-mounted directory on a Linux HPC cluster
- Ask Claude to run any shell command (e.g. nvidia-smi)
- Observe: command shows "running", no output, eventually times out
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
v2.1.70
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗