Unable to use VScode ssh to connet the cluster

Hey everyone,

I'm experiencing some issues with using VScode SSH to connect to my cluster (but I can successfully connect to the cluster through the terminal). Whenever I try to establish the connection, I receive the following error message:

[15:18:56.918] Resolver error: Error: 
	at m.Create (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:584145)
	at t.handleInstallOutput (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:582705)
	at Object.e [as tryInstallWithLocalServer] (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:623656)
	at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async /home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:643708
	at async t.withShowDetailsEvent (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:647428)
	at async /home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:622128
	at async C (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:618634)
	at async t.resolveWithLocalServer (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:621743)
	at async t.resolve (/home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:645036)
	at async /home/qg622/.vscode/extensions/ms-vscode-remote.remote-ssh-0.102.0/out/extension.js:1:720916

I've tried a few troubleshooting steps, but so far, I haven't been able to resolve the issue.

If anyone has encountered a similar problem or has any insights into how to fix it, I would greatly appreciate your help. It's frustrating not being able to connect to the cluster and work on my projects seamlessly.

Thank you in advance for your assistance!

Best regards,

Hello Sachin,

You have reached the maximum number of files on your home directory (114k files > 100k).

You can check this quota with: lfs quota -h -p 161846 /shared/home/svishwakarma

Please, remove files or move them in your project directory. It's often due to conda environment (conda create a lot of hard links).

Best regards.


I deleted the environment, and check that it's below the limits

lfs quota -h -p 161846 /shared/home/svishwakarma
Disk quotas for prj 161846 (pid 161846):
     Filesystem    used   quota   limit   grace   files   quota   limit   grace
                 969.4M    100G    150G       -   11143  100000  150000       -

But when I build a new environment, it still gives me the error saying no space left

[Errno 28] No space left on device: '/shared/home/svishwakarma/miniconda3/pkgs/idna-3.4-py39h06a4308_0.conda'

Best regards

------------------------ Edit ---------------------------
I remove the miniconda, and re-download it. When I try to build the new environment, it still gives this error saying no space left while there's still lots of memory left.
Also, I still couldn't connect the cluster through VScode, and this time there's no output/error/message. It just keeps letting me input the password,

Hello, I have a similar issue on my project sordanlr

every time I launch some scripts, I get an error like:

OSError: [Errno 28] No space left on device: '/shared/ifbstor1/projects/sordanlr/analyse_balancing/3_miniphylo/podosporaceae/sorties_busco/podset-2/podset-2/run_sordariomycetes_odb10/busco_sequences/single_copy_busco_sequences/40005at147550.faa'

but if I check my quota, I still have much space free :

Disk quotas for prj 160573 (pid 160573):
Filesystem used quota limit grace files quota limit grace
4.119T 4.883T 7.324T - 1164837 5000000 7500000 -

I check and my command is quickly responding (If I delete something, the command tells me immediately that I have more space, etc.)

I don't understand, and I don't think that there is a problem on my side

Best regards,

Lucas Bonometti

On the same issue, I had some arrays from my job arrays that were not even launched

We are facing an issue with the storage.
We are still working on this.
See Aucun espace disponible sur le périphérique - #6 par nc-support

Sorry for the inconvenience