Just to tinker with it, last night I installed the Android Studio/SDK, and both during install and use, it repeatedly blew my 2Gb /tmp partition. Is there any way to tell t
You can use a file for your /tmp
:
as root:
create a file the desired size ((example for a 10 GiB /tmp size):
dd if=/dev/zero of=/path/to/your/tmp_dir bs=1024M count=10
create a filesystem on it:
mke2fs -j /path/to/your/tmp_dir
the partition is ready, mount it:
mount -t ext3 -o loop /path/to/your/tmp_dir /tmp
source : https://www.yourhowto.net/increase-tmp-partition-size-linux/
Did a little poking around in the code. The solution is to to start the JVM with a command-line argument that overrides the default tmpdir path:
-Djava.io.tmpdir=whatever
There may be more subtle ways to do it but all I did was edit .../android-studio/bin/studio.sh to replace
VM_OPTIONS=""
with
VM_OPTIONS="-Djava.io.tmpdir=/mnt/disk5/android/tmp"
I fought with the "no space left on device" problem for almost a week. (I will not be beaten!) I tried everything I found here and on other sites and the problem continued. I finally got Android studio completely installed and working correctly using the following approach:
PackageOperation01
on a partition with 100G space.tmp
directory and removed everything I felt was safe to remove, including PackageOperation01
folder.tmp
directory I created a link pointing to the new PackageOperation01
folder I had created.PackageOperation01
. This allowed me to install ALMOST everything.I still had two errors (.."no space..."). Going back to the tmp
directory I found my link to PackageOperation01
had been removed by the installer and a new directory named PackageOperation07
had been created.
PackageOperation07
from tmp
and created a new folder named PackageOperation07
on my large partition beside PackageOperation01
.PackageOperation01
folder and created a new link to the PackageOperation07
folder.This time Android Studio installed with no errors.