The FACT version you are using

d5466a8

Your question

I have set up FACT_core in a VM and I can start FACT and access the web interface. The VM has a 20GB root disk, out of which 11GB are used. There is a dedicated shared folder with sufficient space mounted at /media/data/fact_fw_data:

# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             16G     0   16G   0% /dev
tmpfs           3.2G  940K  3.2G   1% /run
/dev/vda1        20G   11G  7.7G  59% /
tmpfs            16G  1.2M   16G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
fact_fw_data    1.8T  1.4T  396G  78% /media/data/fact_fw_data
overlay          20G   11G  7.7G  59% /var/lib/docker/overlay2/e824123f17480fd50f22717be15114fd73ff009d2b14b3810b060875634afd16/merged
overlay          20G   11G  7.7G  59% /var/lib/docker/overlay2/17726deabcc8f49a8da02e129c8d1b9157ff1ab9f1787822c1578e751e2b5690/merged
overlay          20G   11G  7.7G  59% /var/lib/docker/overlay2/14b28ca3a61218410e27d8c3fa9f77b6636586927b32d323d79da9f94fc90b7e/merged
tmpfs           3.2G     0  3.2G   0% /run/user/0

If I now upload a ~7.5GB firmware image via the web interface, I can watch the space on the root FS vanishing, until FACT crashes with some variant of "no space left on device". If shut down FACT during the upload the disk usage of the root file system returns to the initial 11GB again, so it is cleaning up, what I assume to be, the partially uploaded files.

Is there any way to configure FACT to store whatever is causing this issue inside the fact_fw_data directory? Is there an implicit assumption that the root fs should have the space to store a temporary copy of a firmware image being uploaded?