I’ve noticed after CyberPanel update to a recent version that upgrade.py script created a file /usr/.tempdisk of 1.5G for loop mount on /tmp, /var/tmp.
Can I ask the reasons behind this?
Is it safe to revert that change back to casual fs or at least change its size?
Thanks, that explains reasons. Still sounds like a waste of space for me. Wouldn’t tmpfs be better for /tmp? I don’t run many sites on CyberPanel, but my /tmp usage are usually only around 10-15 Mb while file with FS are strictly 1.5G. Probably should ask a feature request for custom size and/or tmpfs.
Where you can adjust maximum allowed RAM used by changing size= part. Reboot and you can rm /usr/.tempdisk.
If wish to keep on disk but less in size, do the following:
Stop all your services (mariadb, litespeed, etc).
umount /var/tmp && umount /tmp
rm /usr/.tempdisk
dd if=/dev/zero of=/usr/.tempdisk bs=1M count=XX (where XX are wanted size in Mb)
@NStorm
I can also use this to increase the /tmp partition?
Mine if 1.5GB (the default size) and I’m constantly getting core dumps in it so I have to delete those so that /tmp doesn’t run out of space.
Could you explain why should I(we) set block size so 1M?