c95fdef0e59b3aa7d70ad400a30480534b103c90
Root cause of nas_audiobooks still flapping after the automount fix: the health check finds the first file in each share via `find -quit` and `cat`s the whole thing within a 10s timeout. That's fine for immich's 13-byte marker and owncloud's 0-byte one, but audiobooks has no such marker - find picked a real 2.9GB audiobook file, which can never fully transfer in 10s regardless of mount health. Switched to `head -c 64k`, which only needs to prove the file handle/NFS path is alive. Confirmed: the mount was never actually unhealthy post the automount fix, this test methodology was generating the "stale" verdicts (cat exit=124) itself. Also captures and logs/alerts the actual find/head error text now instead of a generic "stale/unreachable" guess, so any future real failure is diagnosable without SSH archaeology.
docker-infrastructure
Languages
Shell
58.2%
Python
28%
JavaScript
10.5%
HTML
2.3%
DIGITAL Command Language
0.6%
Other
0.4%