Hello everyone, I am building Flink, and I noticed...
# troubleshooting
p
Hello everyone, I am building Flink, and I noticed that we have an extra
/mnt
filesystem for builds running on Apache Flink. But, when I clone the same code to a different repo, and use the same github runners, I do not have the extra filesystem available. Due to this, the tests are failing as the disks are getting full. Anyone knows why the filesystem would be different even though its the same github runners? Example of failing build (See module: misc). The Post-build Disk info shows 100% memory -
Copy code
Run df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay          73G   72G  707M 100% /
tmpfs            64M     0   64M   0% /dev
shm              64M     0   64M   0% /dev/shm
/dev/root        73G   72G  707M 100% /__t
tmpfs           1.6G  1.2M  1.6G   1% /run/docker.sock
Comparing the filesystems. See filesystem on my github repo (you can view this in the Initialize Job Phase of E2E-1 tests since they do not run in container) -
Copy code
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        73G   54G   19G  75% /
tmpfs           3.9G  172K  3.9G   1% /dev/shm
tmpfs           1.6G  1.1M  1.6G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda15      105M  6.1M   99M   6% /boot/efi
tmpfs           795M   12K  795M   1% /run/user/1001
Comparing with the filesystem for an Apache Flink run (log - See the extra /mnt disk)-
Copy code
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        73G   51G   22G  70% /
tmpfs           7.9G  172K  7.9G   1% /dev/shm
tmpfs           3.2G  1.1M  3.2G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda15      105M  6.1M   99M   6% /boot/efi
/dev/sdb1        74G  4.1G   66G   6% /mnt
tmpfs           1.6G   12K  1.6G   1% /run/user/1001