Error: no space left on device when I try to update.

[prometheous]

I'm guessing this is because df -h shows / at 100% capacity. I have plenty of unused space on the disk, though. I want to allocate more space to the needed directory. The only thread I found on here were people suggesting to hunt down big files and delete them. All they say is use 'du' command. Well that pulls up 90k files. Come on. How to I just add more space ? This is stupid. It was basically full immediately after install and it's a 1TB drive cloned from a 500gb drive with unallocated space given to sda3. I attached results of df -h and lsblk to try and help everyone understand.

 

[dcsapak]

you probably can increase the lv size of the root lv and increase the fs size on it with the lvm tools (e.g. lvchange etc) but since this is the root fs, you'd have to do it via a live cd i guess (not so sure about that)

 

[H4R0]

This usually happens if users create backups on the local storage.

See if there are any backups on local storage.

Move them to a proper storage.

 

[prometheous]

This usually happens if users create backups on the local storage.

See if there are any backups on local storage.

Move them to a proper storage.

So you're right, I did do that. Since I've made a ZFS mirror for backups. I removed the foolish backup I made, still having the same issue. Any Idea how to allocate that space so I can update?

 

[H4R0]

So you're right, I did do that. Since I've made a ZFS mirror for backups. I removed the foolish backup I made, still having the same issue. Any Idea how to allocate that space so I can update?

Removing backups should free the space.

Make sure there are no backups under /var/lib/vz/dump left.

Please post the output of "du -hs /var/lib/vz/*"

 

[prometheous]

Removing backups should free the space.

Make sure there are no backups under /var/lib/vz/dump left.

Please post the output of "du -hs /var/lib/vz/*"

lol this is so frustrating. I can't find the item taking up all of the space.

 

[H4R0]

Okay it's not backups then.

Go to "/var/log/" and delete some file >= 5mb (or move it)

Then run "apt update && apt install -y ncdu"

In case this fails you have some process constantly writing to your disk and filling it in no time.

Run "ncdu -x /" and it will show you where the files are.

 

[prometheous]

Okay it's not backups then.

Go to "/var/log/" and delete some file >= 5mb (or move it)

Then run "apt update && apt install -y ncdu"

In case this fails you have some process constantly writing to your disk and filling it in no time.

Run "ncdu -x /" and it will show you where the files are.

So check this out, not sure how to rm this. or view it. I recall seeing something like this that was 94GB .

 

[apoc]

Check /lib/modules.
They fill up a lot of space over the time.
This is the reason why I have created a cleanup-script. You can find it here (scroll to the end):
https://forum.proxmox.com/threads/lib-modules-filling-up-hard-drive.39199/

 

[prometheous]

Check /lib/modules.
They fill up a lot of space over the time.
This is the reason why I have created a cleanup-script. You can find it here (scroll to the end):
https://forum.proxmox.com/threads/lib-modules-filling-up-hard-drive.39199/

That's not it

 

[apoc]

check the journal in /var/log/journal
that also can take up significant space