This discussion is archived
1674 Views 2 Replies Latest reply: Jul 21, 2010 10:22 PM by kiggs
Currently Being ModeratedJul 21, 2010 8:46 AM (in response to kiggs)Welcome to Apple Discussions,
Apple's implementation of the FileVault sparsebundle's image apparently results in this peculiar observation - See this thread:
The apparent volume size of a mounted sparsebundle image is a "potential" size, which can be much larger than the current HD space occupied by the sparsebundle (hence the "sparse" in the name). Apparently the potential volume capacity of the mounted image can even be set larger than the HD itself, though it could obviously never be filled to that capacity by files because the sparsebundle could not grow large enough to hold them. What is also unusual in FileVault is that apparently a large fraction of the image capacity gets marked as "used" even before any files have been added to it, as described in the link above.
I guess the bottom line is that when you GetInfo directly on a FileVault Home (which is the mounted image), the "capacity" will be a number twice the size of the HD, the "available" number is probably accurate, and the "used" number is not meaningful because it reflects more than just the contained files.
If do want to see the size of the contained files, you could open a Finder window into the FileVault Home (showing the Documents, Music, Pictures folders, etc), and then type Command-A followed by Command-option-I. You will get an "Inspector" window which should show the total space used by the files, excluding the Trash.Mac Mini, Mac OS X (10.6.4)