[glynnw]

I am using a 2 Terabyte hard drive for music storage and it is working fine. I just have a theory question (I hope).  When I click on properties it shows the "size" as 1.19 TB which is correct.  When I look at "size on disc" it says 8.40 TB.  I did a little search and this is normal - "size on disc" looks at a lot of other things and counts them. My question is this:  How can a 2 TB disc contain 8.4 TB of stuff as shown in "Size on disc" under properties?

[glynnw]

I may have an answer from a computer pro friend I called earlier.  Actually "Size on disc" is a bad description.  It indicates the size of the files without pointers.  The NFTS system uses "pointers" to replace zeros when storing the file on the hard disc. It is a form of compression, but only of zeros, so it doesn't change the sound.  I could change the storage directions to eliminate this compression of zeros, but then I would indeed need a 10 TB disc and bigger as I add more music.  I would imagine this is true for almost all of us using a computer for storage and playback.

[srb]

Something's not quite right with the disk "reporting".  Size and Size on disk are usually very close with large files and Size on disk is larger with many small files.

A small 1KB text file will use the entire allocation unit cluster size, whether 4KB or 64KB.  But on my NTFS music drives, which are relatively large files, the Size and Size on disk are always very close in number of GB.

I've never seen Size on disk reported to be more than the total drive capacity.  Is this disk part of a RAID or JBOD array?

Steve

[glynnw]

It is a 2 TB disc that is mirrored on another in a NAS case.  Even with this oddness, my system playback is fine.  I use Teracopy to place items on this disc (I initially rip to yet another disc) and my computer friend felt this might be why the size on disc was so large.  On the disc to which I initially rip the size and size on disc are indeed the same.