Samba HDD Capacity False Reading

[pcristi]

....
The same problem exists on this machine it cannot copy larger files. I tried to copy a 1.8GB file to the q10 and I get the not enough disk space error.
Disk space reports are all over the place for the samba drive. They do report correctly for Windows machines (both remotely and local).

You can try this on your machines, you will get different results between builds 1809 & 1903.
Got to a command prompt and map a drive to the Q10, I mapped z drive. At the prompt type (you can use your IP address) eg: net use z: \\192.168.x.x\share

Now type at the prompt:-  wmic logicaldisk get size,freespace,caption

With the drive still mapped, you can also try this from the PowerShell Prompt:-  get-psdrive | Where Free*

 Going into the share in file explorer and selecting properties on the folder does seem to give the correct used space.

From my point of view  PowerShell  get-psdrive | Where Free* is report correct for z: \\192.168.x.x\share

Code: [Select]

Name      Used (GB)          Free (GB)           Provider       Root
-----     ----------         ----------          -----------    --------
Z         0,00               0,92                FileSystem     \\192.168.x.x\shareshare is tmpfs as can see on smb.conf

Code: [Select]

[share]
hide dot files = yes
hide files = /.*/lost+found/
available = yes
browseable = yes
create mask = 0777
directory mask = 0777
path = /mnt
writable = yes
valid users =
guest ok = yes
force user = root From adb shell df

Code: [Select]

tmpfs                         964752         0    964752   0% /mnt

[Joker]

Nice one pcristi on remapping the drive to sda(x), this also worked for me. Although really a work around for a problem that does not exist on 1809 build.
The disk reporting results are different from Build 1809 and later builds.
Yes, you are right the Powershell command on the later builds does give the correct disk info.
My results->    z: \\192.168.x.x\share   y: \\192.168.x.x\share\ media_rw\sda1

Build 1809

Command Prompt
Caption  FreeSpace             Size                 
Y:       18446744073709550592  18446744073709550592 
Z:       18446744073709550592  18446744073709550592 
Powershell
Name           Used (GB)     Free (GB) Provider      Root                                                                                                           
----           ---------     --------- --------      ----                                     
Y                   0.00 ...9869184.00 FileSystem    \\192.168.x.x\share\media_rw\sda1                                                                                           
Z                   0.00 ...9869184.00 FileSystem    \\192.168.x.x\share                                                                                                         

Build 18917 (20H1)

Command Prompt
Caption  FreeSpace     Size           
Y:       907374997504  1000202039296 
Z:       991301632          991301632     
PowerShell
Name           Used (GB)     Free (GB) Provider      Root                           
----           ---------     --------- --------      ----                               
Y                  86.45        845.06 FileSystem    \\192.168.x.x\share\media_rw\sda1         
Z                   0.00          0.92      FileSystem    \\192.168.x.x\share                       

[B16 KJR]

Hi

Many thanks for all the replies, but I'm afraid that using Powershell commands and suchlike, are a bit beyond my technical ability !!

Joker, you did say that you could confirm that there is a problem with the later Windows 10 builds, do you think this is something that Microsoft will be aware of and are likely to fix ?  Is there any simple way around this problem  ?

[Joker]

[Mount81]

Maybe a nooby question, but does this drive mapping have any impact on SAMBA transfer speeds?

[B16 KJR]

Hi

Many thanks for the detailed simple instructions Joker, I have done as you suggested and it is all working again. It didn't reconnect to the drives automatically after a restart, even though I ticked the 'reconnect at sign in box' but that may resolve itself though updates hopefully ?

Doing it this way is very handy, as I can now see exactly how much space is left on the HDD's when looking at them via 'This PC'. I just disconnected the old mapped drive letters and paths and they seem to have vanished, I did try the cmd prompt Z:/d but it said it couldn't find them ?

I will now set up my PC the same way and then see if I can get the 1903 update again, but I don't know if it will be available as I had it then rolled back ?

pcristi, apologies, I didn't pick up on the fact that you had already offered the solution, I was getting really confused by that stage.

Thanks to everyone who offered their help.

Kenny

[Joker]

[Joker]

Maybe a nooby question, but does this drive mapping have any impact on SAMBA transfer speeds?

Nope, no noticeable difference, same crappy speeds. But at least it works!

[pepepapa]

Hi, the other day I went to copy some video files to the q10 pro network and it would not let me because it said that there was not enough space in the shared folder when I have more than 2tb free on the hard disk.
Does anyone know why this happens?

[pepepapa]

By the way, in my Windows PC has been updated to the 1903 version, will it have something to do? the samba configuration?

[pepepapa]

I've tried teracopy and it seems to be going well.
with the windows explorer is not going well

[B16 KJR]

Joker, do you know if there is any way to get the 1903 update back on my PC, given that I already had it then rolled back to the 1809 version ?

Also thanks again to pcristi for all his help.

[Joker]

Sure, you can use the Windows Media Creation Tool or the update assistant. If you follow this link it should step you through it.

https://www.microsoft.com/software-download/windows10

[Kantor]

Thanks a lot, Cristi ! It works indeed by mapping.

[CookiePuss]

I'm having this same exact issue right now. Everything was perfect for the last 2 years transfering to both my HD10 and KDLinks boxes. Then Windows just installed a few updates for Windows 10 that is giving me the same error about not enough space. The updates installed were:

Feature update to Windows 10, version 1903
KB4505903
KB4506991

Ever since then I can't use Samba anymore. I tried a system restore but it didn't go through, said it might be my anti-virus blocking it. Then I tried manually uninstalling the updates but it made no change. It has to be one of the updates thats doing it as I'm trying to send to two different boxes/drives and am getting the same error about no space.

I'm going to try re-mapping that was mentioned in this thread. What a pain in the ass Microsoft is.

UPDATE: Thank you so much to Pcristi for the fix and to Joker for dumbing it down to a point I could understand what to do. You guys are the absolute best! I mapped both drives and I can transfer files to them again and even see how much disk space they have under My PC. 

P.S. I Hate You Microsoft!