Currently Being ModeratedApr 27, 2012 2:39 PM (in response to Oliver Hoeveler)
Are you using Time Machine to do those backups? Does the Time Machine panel of System Preferences show a recent successful backup? If both those are true, have you changed many files? Time Machine only consumes much additional space if files on your Mac change.
Currently Being ModeratedApr 29, 2012 1:31 PM (in response to William Boyd, Jr.)
Yes, I am using Time Machine. The panel shows a successful backup and I have changed a lot of files.
What I am asking for is that the available space in the time machine panel does not change. It shows the same amount during backups for weeks. Whaen no backup is running I can only see some dashes...
Currently Being ModeratedMay 2, 2012 2:07 PM (in response to William Boyd, Jr.)
I do not think so. As the TM panel does not show the disk space as no backup is running. I had the same problem in the past. Disconnecting the TM and connecting again did help but this time the problem does not dissappear....
Currently Being ModeratedMay 2, 2012 7:38 PM (in response to Oliver Hoeveler)
Oliver Hoeveler wrote:
I do not think so.
Do you think so based on your following statement or because of something else?
As the TM panel does not show the disk space as no backup is running.
It won't, as the "sparsebundle" file containing your backups isn't mounted when Time Machine isn't running. You can mount that yourself. Select your Time Capsule from a Finder window sidebar, then the "Data" volume (presuming you didn't change its name). In the Data volume double-click the "sparsebundle" file to mount it. You should now see space reported in the Time Machine panel of System Preferences.
Currently Being ModeratedMay 2, 2012 8:32 PM (in response to Oliver Hoeveler)
If you have deleted files from your Mac in the past.....these files will usually stay on the Time Capsule for some period of time. Could be months or many months.
But, at some unknown point in time....Time Machine will delete those files from the backups to clear space. When it does that, you would think that the sparsebundle would then show more available space on the drive....but it does not do that.
Sparsebundle files are curious items......they "grow" as files are added, but they do not appear to shrink when files are deleted.
For example....The sparsebundle file might have grown to 100 GB. But Time Machine deleted 5 GB. The sparsebundle file will continue to show as 100 GB until the space that was gained when the files were deleted fills back up to 100 GB. At that point, the sparsebundle file will start to "grow" again.
This is very likely what is happening on your Time Capsule at this time.
If you have been checking your backups by going into Time Machine and everything appears to be normal, then I would not be concerned.
It is possible to "shrink" the sparsebundle file and have it display the actual space that is being used. But, you have to use Terminal commands to do this.
We can give you the commands to "compact" the sparsebundle if you want them....but unless you are an experienced Mac programmer, I would stay away. The Terminal is a very scary place.
Currently Being ModeratedMay 2, 2012 9:38 PM (in response to William Boyd, Jr.)
If Oliver tells us that he has never deleted any files from his Mac and there is plenty of free space on the Time Capsule.....then I am stumped on this one and we'll call in Pondini to rescue us all.
Currently Being ModeratedMay 3, 2012 12:53 PM (in response to Bob Timmons)
Thanks for all your support folks.
Maybe I was a little missunderstandable. I have added a lot of new ripped songs to iTunes and did not delete a lot of files.
When I open the TM panel when no backup is running I can see "Available: --" Only the two dashes are displayed. The display will change to "Available: 512.98 GB" if a backup is starting. The panel is showing this 512.98 for weeks.
Currently Being ModeratedMay 24, 2012 1:46 PM (in response to William Boyd, Jr.)
I have disconnected my Time Capsule Disk in the TM paneand re-connected again. Now everything is fine...
This is probably a workaround.
Thanks for all your engagement, very appreciated :-)