Minimum Free Disk Space setting not working/respected?

Got a ticket:

Description of the issue

(...)
I have a Pixel 2 XL running the Syncthing v0.14.50 app with a folder on its
internal storage sync’d to said shared folder from home PC mentioned
above…with conditions to only sync on certain wifi AND AC power.

Syncing works well, however, my issue is that Minimum Free Disk Space
setting doesn’t seem to be respected…this is where I assume I possibly am
understanding the setting incorrectly or have it set up incorrectly…

In the app on the phone, there are two locations to adjust the Minimum Free
Disk Space that I can see. One is under the gear icon on main WEBUI and the
other is under the Advance section in the edit menu of the folder being
sync’d.

My phone is advertised as the 128GB model (110GB usable). Of this internal
capacity, I have roughly 80GB free…The default value for both of the
Minimum Free Disk Space settings in the Syncthing app was 1%; is this 1% of
the usable 110GB or 1% of the 80GB free space? Anyways, I want there to be
a total of about 5GB of free space left on the phone after all the syncing
(which obviously I understand you can’t fit 500GB into 80GB and thus
syncing stops until more free space is made available), which setting
should I change the folder or the one in the main setting…or both?

I’ve attempted various values in percentages and absolute values in MB and
GB yet when I wake up in the morning I have a notification on my phone of
low disk space and Google play services among others keep crashing due to
this…generally left with anywhere from 49 MB or less to maybe at most 120
MB or so…
(...)

Version Information

App Version: ?
Syncthing Version: v0.14.50
Android Version: ?
Device manufacturer: Google
Device model: Pixel 2 XL

Android Log

adb shell / logcat
or MatLog (search on GitHub) output

[cmcooper1980]

OK great…thank you again!

On Sun, Jan 27, 2019 at 1:56 PM Catfriend1 [e-mail] wrote:

Release is there on GitHub, GPlay will follow soon.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Catfriend1/syncthing-android/issues/277#issuecomment-457948789, or mute the thread https://github.com/notifications/unsubscribe-auth/AeZQp7rlXBSFZu1yjE-mFQRpAlnb46w5ks5vHgRlgaJpZM4aRslR .

[cmcooper1980]

OK thanks, I will try these suggestions.

On Sat, Feb 2, 2019 at 5:30 PM Catfriend1 [e-mail] wrote:

It’s not that easy. I’ve deleted the debug version as the code changes went in the release so there’s no difference from technical view. What may cause the inaccurate free space evaluation is the parser as gson glitches and returns for example 4.5gb as 4.6 gb due to the internal scientific representation of the float value fields in the config which are like 4.5e+8 in that case. We need to transition to a different parser, for example, Jackson to fix this as In didn’t found a reliable way to workaround this in gson. Doing this may introduce a lot of bugs in the initial transition step as Jackson handles the whole deserialization of config values differently… We’ll do this later. Try experimenting with values then, e.g. write 2 gb instead of 2000 mb and be sure to exit the app after you changed something like this from the native web ui. This will lower parsing glitches’ impact.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Catfriend1/syncthing-android/issues/277#issuecomment-460008600, or mute the thread https://github.com/notifications/unsubscribe-auth/AeZQp9kysjLoub3aj1B_GJYHKy0yrGmiks5vJh-IgaJpZM4aRslR .