Gitlab remote: fatal: write error: No space left on device

Question

I get the following error when I do git push -f origin master

warning: redirecting to https://gitlab.iit.it/muhammad.mehdi/memex-app.git/
Enumerating objects: 1048, done.
Counting objects: 100% (1048/1048), done.
Delta compression using up to 12 threads
Compressing objects: 100% (618/618), done.
remote: fatal: write error: No space left on device

I did df -h and I get the following

Filesystem      Size  Used Avail Use% Mounted on
udev            7.7G     0  7.7G   0% /dev
tmpfs           1.6G  2.8M  1.6G   1% /run
/dev/nvme0n1p6  227G  109G  107G  51% /
tmpfs           7.7G  148M  7.5G   2% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.7G     0  7.7G   0% /sys/fs/cgroup
/dev/loop1      9.2M  9.2M     0 100% /snap/canonical-livepatch/95
/dev/loop3       56M   56M     0 100% /snap/core18/1997
/dev/loop5      100M  100M     0 100% /snap/core/10908
/dev/loop4       56M   56M     0 100% /snap/core18/1988
/dev/loop6       46M   46M     0 100% /snap/dotnet-runtime-50/11
/dev/loop8       62M   62M     0 100% /snap/core20/904
/dev/loop7       65M   65M     0 100% /snap/gtk-common-themes/1514
/dev/loop9      218M  218M     0 100% /snap/gnome-3-34-1804/60
/dev/loop10     219M  219M     0 100% /snap/gnome-3-34-1804/66
/dev/loop0      926M  926M     0 100% /snap/android-studio/101
/dev/loop11      63M   63M     0 100% /snap/gtk-common-themes/1506
/dev/loop12      16M   16M     0 100% /snap/kolourpaint/56
/dev/loop13     163M  163M     0 100% /snap/gnome-3-28-1804/145
/dev/loop15      33M   33M     0 100% /snap/snapd/11402
/dev/loop14     291M  291M     0 100% /snap/kde-frameworks-5-qt-5-14-core18/4
/dev/loop16      52M   52M     0 100% /snap/snap-store/518
/dev/loop17     111M  111M     0 100% /snap/xournalpp/48
/dev/loop18     200M  200M     0 100% /snap/code/60
/dev/loop19     111M  111M     0 100% /snap/xournalpp/42
/dev/loop20      62M   62M     0 100% /snap/core20/975
/dev/loop21      51M   51M     0 100% /snap/snap-store/481
/dev/loop22     132M  132M     0 100% /snap/dotnet-sdk/116
/dev/loop23     324M  324M     0 100% /snap/kde-frameworks-5-qt-5-15-core20/14
/dev/loop24     113M  113M     0 100% /snap/kolourpaint/59
/dev/loop25     426M  426M     0 100% /snap/pycharm-community/232
/dev/loop26      33M   33M     0 100% /snap/snapd/11107
/dev/loop27     426M  426M     0 100% /snap/pycharm-community/233
/dev/nvme0n1p1   96M   53M   44M  55% /boot/efi
tmpfs           1.6G   20K  1.6G   1% /run/user/125
tmpfs           1.6G   68K  1.6G   1% /run/user/1001
/dev/loop28     100M  100M     0 100% /snap/core/10958
/dev/loop2      1.1G  1.1G     0 100% /snap/root-framework/130

I have 114 GB of free disk space:

How do I solve this issue? I have deleted so much stuff from my home folder and the picture clearly says I have free space. Then what's the problem?

Answer 1

The purpose of the git push -f origin master command is to update a remote repository running somewhere other than your own laptop so that its copy of the repository you are working will contain the changes you've made to that repository. The existence of this remote repository is what allows collaboration by multiple programmers on a single set of source code.

That error message is telling you that the remote server that you are attempting to push (copy, update) your code to is out of disk space on whatever disk volume it is storing the Git repositories that it manages.

Since iit.it looks to me like a company that would not be in the business of hosting Git repositories for other businesses, I assume that this remote Git repository is either being hosted by your company or is being hosted by someone else solely for use by your company. Therefore, what you need to do is reach out to the IT support people at your company to find out what is going on here. It is likely that something needs to be done to free up or add disk space to the server(s) running the remote Git repository.

Answer 2

The "remote:" message here means that the message you're seeing came from the remote side. In this case, the remote side (that is, the Git server) said, “fatal: write error: No space left on device”.

Therefore, the most likely thing to conclude here is that your Git server is out of space. You should contact the party responsible for maintaining that server and ask them to fix the problem. There wouldn't be anything that you could do to fix the problem unless you administer the server.

Answer 3

Your /snap partition is 100% full. We do not know the details of your system configuration, but it is highly likely that the system is not even capable to perform the required operations in order to process the push command.

Try another operation such as a fetch . If the fetch operation also fails for the same reason, it is most likely the lack of local disk space.

Then you can also delete stuff in /snap . If you can, and it works, then that's it.

Can you do git remote -v to make sure you are working against a remote server?