cannot create temp file for here-document: No space left on device...

[Bo Berglund]

On Tue, 9 May 2023 09:19:48 +0100, Colin Law <clanlaw at gmail.com> wrote:

>On Tue, 9 May 2023 at 09:03, Bo Berglund <bo.berglund at gmail.com> wrote:
>>
>> /dev/nvme0n1p6           30G   28G     0 100% /   <== WHAT????
>> ...
>> /dev/nvme0n1p8          259G  215G   31G  88% /home
>> ...
>>
>> My scripts run on thge home partition which is well below being full.
>>
>> What can have happened and how can I fix it?
>>
>> To mee it lokks like / should have 2G free, and also that it should not get into
>> play since the operations are done on /home
>
>I think the reason it is saying 100% is that Linux reserves some space
>on each drive in case the system needs some, in order to prevent the
>OS from crashing horribly.
>It may be /tmp that is being written to.
>I like ncdu for finding where space is being used up.  Install it if
>necessary and run
>sudo ncdu /
>It will show you usage on a folder basis and you can step in to look
>at lower levels. You need sudo if running on / otherwise it errors on
>dirs it cannot read.

I discovered this problem when I just returned home after a 2 week trip.
Now I have seen that apt does not work either for the same reason...

I tried to move all var/log/*.gz files in to $HOME/log/syslogs/ since $HOME is
on another partition. But it did not help...
I tried a simple sudo apt update and it failed with the same error.
The gz files totalled 628 kbytes.

I had ncdu already installed so I tried it:
$ ncdu /var

ncdu 1.14.1 ~ Use the arrow keys to navigate, press ? for help
--- /var --------------------------------------------------
.  19.3 GiB [##########] /lib
.   3.0 GiB [#         ] /log
. 125.7 MiB [          ] /cache
    3.7 MiB [          ] /backups
. 116.0 KiB [          ] /snap
   60.0 KiB [          ] /www
.  32.0 KiB [          ] /tmp
.  28.0 KiB [          ] /spool
e   4.0 KiB [          ] /opt
e   4.0 KiB [          ] /mail
e   4.0 KiB [          ] /local
e   4.0 KiB [          ] /crash
@   0.0   B [          ]  lock
@   0.0   B [          ]  run

The main use in log is log/journal

But the by far biggest user is lib/svn where 17.8 GB is used!

And /var/lib/svn/pc/db/txn-protorevs alone uses up 11.9 GB!

That is in files with extension .rev like 4498-3hg.rev each at 319.4 MiB

Any suggestions on a way out?

-- 
Bo Berglund
Developer in Sweden