Transfer over Samba : no space available??

[nick81]

Hey all

I am on CFW2.1.2 (upgrading tonight to 2.1.4 v1.2) and been facing a weird issue since last week.

When I try to transfer files from my laptop to my Q10 Pro using samba, I get an error saying that there is not enough free space on my hard drive.

I have well over 1TB free and I am able to copy files to the hard drive by removing it from the Q10 and plugging it in an external mount.

Any idea what could be wrong? I've always used Samba to transfer files without any problems...

[nick81]

Updated to 2.1.4 CFW, same issue....

https://ibb.co/6ykHQ7r


Edit: Using Teracopy, I am able to transfer the files... Read online that this could be an isse with how samba reports available space from mounted drives. Does anyone know how to resolve this? I have no problem using teracopy from now on but I am curious to know why the standard Windows copy stopped worklng... Thx!

[Nice Monkey]

If you are running Himedia as a Samba server and client on the PC then the server will report the wrong free space. It did that with Android 5 and still does that with Android 7 despite now supporting SMB v1/v2/v3 instead of just v1. It depend on the application if it will actually look at this or not. Most don't but some (good ones) do. 

See also:
https://www.futeko.com/newforum/index.php?topic=4336.0
Problems are HiSillicon SDK related and common for all brands/platforms using it.

[Mount81]

Isn't this also related to a recent Win10 update?

[Nice Monkey]

Isn't this also related to a recent Win10 update?

I don't think so. What recently changed is that SMBv1 was removed from W10 as a default (can still be added via options). HiSillicon SMB Server under A7 works just fine with that as it now supports SMB v2/v3 too.

What I get reported is -1K of -1K free free. This is the wrong/no HDD size and wrong/no free space reporting. That is very bad as many W10 applications will then refuse to write to it. As far as I remember the old version under A5 was changed to report a fixed positive value. Not good but  still a lot better. So maybe it still does so when connecting via a SMBv1 client (did not try that)?
Using myself Total Commander (excellent highly recommended APP) which still works with it for now even being reported wrong values to it.

I report here not even owning a Himedia player anymore as this is a generic HiSillicon SDK problem. The same behavior on Dinobot, Dune and Egreat players!