4

I have read Why is there such a big difference between "Size" and "Size on disk"? but why is mine so different?

enter image description here

My RAID5 is set at 128kb stripe, the volume is formatted at 64kb NTFS. I would expect the file size to be 64kb, not 1mb.

Edit: A bit of context here: the first screen was from a vhdx formatted as 64kb mounted to a VM. The screenshot below is from the volume of the host where the vhdx sits. This volume is also formatted as 64kb too.

enter image description here

Community
  • 1
codaamok
  • 1,353
  • Down voters please share your knowledge, you clearly know something I don't so put me out of my misery – codaamok Apr 21 '16 at 18:09
  • 3
    I actually think this is a decent question. I do not know the answer to this but I would think it should be 128kb, not 64 (the weakest link).. either way I would think not 1MB. I am curious to the answer too.. – Eric F Apr 21 '16 at 19:11
  • 1
    I noticed the location is on a network area, probably a NAS. If you copy the file locally, how big is it on your harddisk? – LPChip Apr 21 '16 at 19:36
  • @LPChip I've updated the question. Even weirder now... – codaamok Apr 21 '16 at 19:48
  • 2
    About "even weirder now" part: explanation. – Kamil Maciorowski Apr 21 '16 at 20:02
  • This is exactly the same as this question which also has no answer (so it can't be marked as duplicate). – Moshe Katz Apr 26 '16 at 02:46
  • According to this FreeNAS forum post, Windows 7 showed the correct value for files on a network share, while Windows 8(.1) and possibly newer versions show 1MB incorrectly. I'm travelling without any network shares mounted at the moment, so I can't test this myself, but it sounds plausible. – Moshe Katz Apr 26 '16 at 02:48
  • @MosheKatz I'm glad your attention to detail understands this question is still up for grabs. Thanks for sharing – codaamok Apr 26 '16 at 09:40
  • I've been looking through many files on my NAS. Windows seems to commonly report a different size on disk than the NAS does. I expect tthat WIndows is wrong and the NAS is correct. I don't know the reason why, but it could be a bug in Windows or limt or a protocol limitation for "non-local" files. – Amorphous Oct 21 '21 at 01:34

0 Answers0