Server Space Full, Can't Install new storagespace purchased

Zitat von aRaphael

You can also free additional space in /var/log by clearing older journal files, e.g.:

Code

journalctl --vacuum-time=10d

(See man journalctl for additional infos)

Yes I have tried this and it recovered nothing. 0B

Zitat von Valkyrie

I guess you mean swap space? You can test for it with swapon or cat /proc/swaps.

To see which directories occupy most of your storage you can also execute du -h / | sort -h. Depending on your system it could take a while and you should execute it as root, otherwise you will see tons of errors.

I have no idea when it comes to Docker but... if you say your whole storage is gone after installing that one docker container, can't you free up some space in the container itself?

If df -h shows the 879M available, I'm pretty sure you should be able to install the NFS package.

Alles anzeigen

The docker was installed last year December and it has grown to consume almost 34G. Originally after installation then the container size was 1.6GB. Other system applications not installed by me took the remaining space.

I have viewed the swapfile and it has 1024M OB used.

This is the var/lib folderimage9.PNG

Zitat von Olivetti

maybe your system isn't old enough. go there manually.

or go to cd /var/log and screenshot du -h

image10.PNG

Zitat von Olivetti

delete *~ in both ./journal/* subdirs (see #23).

btw what's this docker app causing such a mess?

This is the life saver. Worked. I have been able to install the nfs-common.

Very much thanks, everyone.

I have completed the count. However, I am not sure where I can to see the new space as the server home space says currently attached not available. I have rebooted the server and it's not still available.

Thanks again for your helpimage12.PNG

mount -t nfs STORAGEHOST:/STORAGEPFAD /mnt/storagespace

Use my storage details here for clarity

Zitat von TBT

The docker logs can grow quite a lot if not set in an /etc/docker/daemon.json file. Their (standard) path is:

Code

/var/lib/docker/containers/<container_id>/<container_id>-json.log

So have a look there and delete files which are too big / too many.

Because I do not want the docker logs to grow indefinitely AND because I don't want docker to reside in a sub-sub-directory, I set as /etc/docker/daemon.json:

Code

{
"data-root": "/docker/", 
  "log-driver": "json-file", 
  "log-opts": { 
    "max-size": "10m", 
    "max-file": "3" 
  } 
}

The log-opts part set the max size of the logs. You should probably not use the data-root part, as you would need to stop the daelmon, move everything from /var/lib/docker to /docker and then start again. But the rest is usable.

40GB is really not much space. I would suggest a bigger VPS or RS. If you bought storage space, you need to mount that space before you can use it: https://www.netcup-wiki.de/wiki/Storagespace_mounten

You will probably still need to move your docker folder (if you have used volumes) to the NFS mount, so my daemon.json including the data-root part might still be useful for you. I would however highly recommend getting a bigger VPS or RS instead.

Alles anzeigen

Thanks. Maybe I think that is what I would do.

Thanks very much