NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Size of files/folders vs "size on disk" MASSIVELY different?
Hi there, I'm on my NVX via a windows 8.1 machine, just going through some image folders and tidying up a little, when I realised there is a simply massive disparity between the "size" and the "size o...
- I ran again the volume consistency check manually and it found volume scan was needed, so rebooted with the vol scan, it reported fixed problems...re-ran the scrub - that finished good in approx 7hrs. Problem still there on file count....so I installed TreeSize Pro - to find out in the 100+ folders - which one tripped the size, and low & behold - found the single file showing 16TB in size (yes, impossible on a NAS with only 2.6TB). It was a quickbooks file. Zero clue how, but I opened the file, backed it up, resaved and now the file size reports normal at 58mb. Whew!!! TG for treesize pro finding exactly what file. The wonders of why or how this can happen, but guess any corrupt file can produce strange results.
I am sure CP now will be happy I am not trying to push 17.1TB of data ...thru our unlimited data plan. :)
ReadyAS wrote: There is 80935 files in 592 folders.
In that case, Windows 8 is using 1KB allocation units and Windows 8.1 is using 64KB.
ReadyAS wrote: No, [the du -b result and the Windows Size reports are] different: 352 868 872 447 vs 352 863 936 767 (not so much, but different)
Ah, my mistake.
That difference is a mystery to me as well; I don't know enough about the Linux filesystems to know where the extra ~60 bytes per file (or ~8K per directory) is coming from.
ReadyAS wrote: The difference between W8 and W8.1 [size on disk] is not acceptable in my opinion, but it is Microsoft fault.
I do not know for sure -- this is only a guess -- but I assume that the difference is due to Windows 8.1 being "smarter" about calculating cluster size. Rather than simply accepting the 1KB cluster size reported by the NAS, perhaps Windows 8.1 assumes that the cluster size is the GREATER of that 1KB and some block-size parameter used by SMB. (I don't know anything about SMB, so I can't say exactly what parameter that might be.) If the SMB protocol requires an acknowledgement (or a similar time-wasting action) after every block, it would make sense for Netgear to set the SMB block size to an absurdly high value in order to make transfers happen as quickly as possible... And the original, pre-OS4.2.25, Windows 8.1 size on disk that you posted -- 8498498764800 -- indicates that Windows 8.1 was indeed seeing a huge block size, somewhere around 32MB.
I guess that the SMB block size was decreased in OS4.2.25 to make the Win8.1 size on disk more accurate, but that Netgear couldn't make it as small as the actual 1KB cluster size without hurting the transfer speed too much, so they compromised at 64KB: Close to the correct size on disk, but still fast.
As I said, though, only a guess.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
