Page 1 of 1

smb share reporting incorrect free space.

Posted: Wed Sep 03, 2014 12:46 am
by A93h201
I tried to cooy 15gb to a 1tb usb hdd. Windows said i needed 2gb of more space. Split the files, and they copied with no space issues. Web management of the router showed 900gb free.
Tried drive in fat32 and ntfs, same issue with each. Mutiple files make the 15gb i am trying to copy.

Thanks

Re: smb share reporting incorrect free space.

Posted: Wed Sep 03, 2014 9:28 am
by billion_fan
A93h201 wrote:I tried to cooy 15gb to a 1tb usb hdd. Windows said i needed 2gb of more space. Split the files, and they copied with no space issues. Web management of the router showed 900gb free.
Tried drive in fat32 and ntfs, same issue with each. Mutiple files make the 15gb i am trying to copy.

Thanks
Let make sure I understand, you plugged a hard drive to the 8800NL, (1tb fat32/NTFS) and when you copy a single 15gb file, your computer reports there is insufficient space on the hard drive. even though you have 900gb free

But if you zip the 15gb file into 50mb or 100mb files all files can be copied to the hard drive without any issues.

Is that correct?

Re: smb share reporting incorrect free space.

Posted: Wed Sep 03, 2014 7:43 pm
by A93h201
Sort of.
~30 files with a total size of ~15gb when all copied together windows says not enough space.
If i split the files up in to batches of 8gb and 7gb the copies both complete.

Re: smb share reporting incorrect free space.

Posted: Wed Sep 03, 2014 11:23 pm
by A93h201
Mapped a drive in windows to the share, network drive shows 20mb free space. Drive details under usb shows 880gb free

Re: smb share reporting incorrect free space.

Posted: Thu Sep 04, 2014 9:03 am
by billion_fan
A93h201 wrote:Mapped a drive in windows to the share, network drive shows 20mb free space. Drive details under usb shows 880gb free
What version of windows are you using??

Re: smb share reporting incorrect free space.

Posted: Sat Sep 06, 2014 1:19 am
by simon194
This incorrect volume size reporting in Windows with SMB shares usually happens when a disk drive hasn't been mounted at the root level by the Linux. Whether this is the issue here, I have no idea.