07 Feb 11, 10:06PM
hm. it seems there's still something wrong with the filesize-calculations.
I remember when this was introduced I had this issue and I had something like 50GB free, but the code thought it was less than 0.5MB .. or something like that. The coder of the feature then fixed it, so that I didn't have the problem anymore - but apparently it's still off.
I will take a look into it, thank you for your feedback - sorry for the inconvenience - please try to free up more diskspace until the next release brings a real fix.
I will post back here to tell you what/if I found anything.
I remember when this was introduced I had this issue and I had something like 50GB free, but the code thought it was less than 0.5MB .. or something like that. The coder of the feature then fixed it, so that I didn't have the problem anymore - but apparently it's still off.
I will take a look into it, thank you for your feedback - sorry for the inconvenience - please try to free up more diskspace until the next release brings a real fix.
I will post back here to tell you what/if I found anything.