Emit warning when AFS filesystem detected

Hey,

This was a LXPLUS (CERN cluster) related issue specifically, but yeah, moving the serverInstallPath to a /tmp/user folder solved the problem.

Thank you very much for your time,

Diego

El 10 feb 2025, a las 17:26, Josh Spicer @.***> escribió:

From your log it appears the remote machine is using an AFS filesystem which is known to behave strange with Remote SSH.

Here are some steps https://github.com/microsoft/vscode-remote-release/issues/10445#issuecomment-2462790307 I recommended in the past. In addition, if you can move your serverInstallPath to a non-AFS filesystem, that would likely be the best mitigation.

Please let us know if any of these workarounds help for future folks 🙏

—

Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-remote-release/issues/10680#issuecomment-2648586601, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDWR7HOEWDXL3LHDEPF7DT2PDHMXAVCNFSM6AAAAABWRLDXG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBYGU4DMNRQGE.

You are receiving this because you authored the thread.

Originally posted by @DiegoCostas97 in #10680

No source files or tests are named. Start by tracing how the Remote SSH extension handles serverInstallPath, then determine where AFS filesystem detection could produce a warning. Done means users are warned when the server installation path is on AFS, without affecting non-AFS paths.