SMB disk size upto 6 times larger than file size

[cougarmaster]

I have Freenas 11.2 U6 running with :-
1] 12GB Ram
2] 4 cores
3] LSI HBA
4] 6 x 2TB red label WDdrives - Raidz2
5] SSDx2 Cache for Slog and Cache

Note : - There is already data hope I don't need to redo it please help.

All is running fine and no hicups. It is also running on a VM on xcp-ng server. It is serving 2 people atm and transfer speed are really good and shares to MACs and Windows. The problem is a first and I have built many system like these for clients and haven't had this exact problem. I created all vdevs using GUI nothing from cli and also all shares are SMB. There are no snapshots for datasets or pool and also no snapshot for smb for versioning. So not sure where the problem lies. When showing in properties of a folder in windows 10 the contents are correct but disk size vary from 3 times upto 6 times from what I can see but some folders are fine since LZ4 is enabled it show smaller sizes. In shell of freenas there are no hidden files or folders in the shares. Also yes there is an iSCSI share for other VM connected to xcp-ng it is on its own dataset. Please at least let me know it is a windows 10 pro problem ;)

TIA
Eric

 

[anodos]

Try setting the share-level SMB auxiliary parameter allocation roundup size = 0 and restarting the SMB service.

 

[cougarmaster]

Thanks anodos do I do his for each share or in smb service itself?

 

[cougarmaster]

Try setting the share-level SMB auxiliary parameter allocation roundup size = 0 and restarting the SMB service.

OMG Thanks I will do it in each share !!

 

[cougarmaster]

Just out of curiosity even if we didn't do this will it affect the files in anyway or how storage is calculated in windows?

 

[anodos]

Just out of curiosity even if we didn't do this will it affect the files in anyway or how storage is calculated in windows?

It has no real effect on clients. It just impacts user perception when looking at that field in file explorer.

 

[cougarmaster]

It has no real effect on clients. It just impacts user perception when looking at that field in file explorer.

Thanks so much anodos really appreciate your help.

 

[thatflashcat]

I've been wondering about this for a while, good to know that the high file sizes aren't accurate.

 

[anodos]

This parameter is changed in 11.3. Feel free to try out the beta.