From: Müller L. <Lau...@un...> - 2011-05-20 22:00:20
|
Am 20.05.2011 um 22:39 schrieb John Wittkoski: > On Thu, May 19, 2011 at 11:04 AM, Müller Laura <Lau...@un...> wrote: > Am 19.05.2011 um 07:15 schrieb Frank Lahm: >> >> Starting with afair 10.6.4 backupd will resize the image at will up to >> the maximum available space on the volume. Precreating doesn't help. >> > > Yes, you are right. I had the same problem myself, but if backupd does not have write access to the Info.plist and Info.bckp files inside the sparsebundle it can not resize the image to the maximum available space anymore. I recently checked the volume while TimeMachine was doing a backup and the size is still the same: > > > > Do you know if the Info.plist and Info.bckp files are used for anything else? > > That is, making them read only prevents the sparsebundle from being expanded but does it break any other needed operations? > > --John As far as I know this hack doesn't have any negative side effects, but you should keep in mind that it's an ugly hack and not a clean solution. Last saturday I found out that blocking write access to these two files keeps backupd from expanding the sparsebundle to the maximum available size immediately on the next run. Since then everything is working fine. There isn't much information inside the Info.plist file, only some properties to describe the format and the size of the sparsebundle. Misi:~# cat /DataVolume/shares/Misi-Backup/Mausi.sparsebundle/Info.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>band-size</key> <integer>8388608</integer> <key>bundle-backingstore-version</key> <integer>1</integer> <key>diskimage-bundle-type</key> <string>com.apple.diskimage.sparsebundle</string> <key>size</key> <integer>536870912000</integer> </dict> </plist> But you should keep in mind that backupd is no longer able to shrink the sparsebundle size in case you put something else on the filesystem eating up the space required to hold the sparsebundle when it reaches it's maximum size. Provided that you keep an eye on disk usage, I'm quite sure it won't break anything in the future. |