On 2018-02-24, at 6:04 PM, @lbutlr <krem...@kreme.com> wrote: > On 2018-02-24 (17:03 MST), Michael <keybou...@gmail.com> wrote: >> >> To clarify: with the default 8 MB band size, the same behavior of assuming >> that the space on the image is the same as the space on the host drive, > > You said "The sparse bundle was the size of the partition minus a small > amount ", so what are you expecting the free space to report? > > I only use a few sparse bundles, they are set to be maximum of 4.7GB and > they report the proper amount of free space as maximum Size of bundle - space > used on bundle, as I would expect. > > If you are making a custom sparse bundle with a custom band size I would not > be at all surprised if something like Time Machine got very confused by that. > Time machine is not just any app, and it has deep hooks into the system. > > As for deleting data from Time Machine, this is often tricky and just because > you think you deleted something doesn't mean you did. What tool are you using > to delete files to free up space? > > AFAIK, Time Machine only supports using sparse bundles that 1) it creates and > 2) are on network shares. Could be wrong, it's not something I've spent a lot > of time on. Time Machine is my primary backup, but that is only because it is > convenient. The backup I rely on is Backblaze.
I am certain that I'm actually deleting the large file. The tool that I am using is Time Machine itself. Console log shows: Feb 23 21:23:44 keybounceMBP com.apple.backupd[26765]: Deleted backup /Volumes/TimeMachine/Backups.backupdb/Keybounce's MacBook Pro/2017-11-09-235918 containing 51.36 GB; 56.22 GB now available, 7.69 GB required Feb 23 21:23:44 keybounceMBP com.apple.backupd[26765]: Deleted 3 backups containing 53.48 GB total; 56.22 GB now available, 7.69 GB required Feb 23 21:23:44 keybounceMBP com.apple.backupd[26765]: Backup date range was shortened: oldest backup is now Nov 16, 2017 Feb 23 21:23:48 keybounceMBP com.apple.backupd[26765]: Copied 8 items (1 KB) from volume Macintosh HD. Linked 21. Feb 23 21:25:01 --- last message repeated 4 times --- Feb 23 21:27:47 keybounceMBP com.apple.backupd[26765]: Copied 405 items (1.54 GB) from volume New Main. Linked 6550. Feb 23 21:28:08 keybounceMBP com.apple.backupd[26765]: Copied 2 items (Zero KB) from volume UserData. Linked 13. Feb 23 21:28:11 keybounceMBP com.apple.backupd[26765]: Copied 2 items (Zero KB) from volume rawTimeMachine. Linked 5. Feb 23 21:28:16 keybounceMBP com.apple.backupd[26765]: Copied 5 items (33 bytes) from volume Sierra10-12test. Linked 19. Feb 23 21:29:32 keybounceMBP kernel[0]: hfs: set LowDisk: vol:TimeMachine, freeblks:17670, warninglimit:19200 Feb 23 21:29:32 keybounceMBP KernelEventAgent[136]: tid 54485244 received event(s) VQ_LOWDISK (4) Feb 23 21:29:32 keybounceMBP KernelEventAgent[136]: tid 54485244 type 'hfs', mounted on '/Volumes/TimeMachine', from '/dev/disk4s2', low disk Feb 23 21:29:33 keybounceMBP kernel[0]: hfs: set VeryLowDisk: vol:TimeMachine, freeblks:12710, dangerlimit:12800 Feb 23 21:29:33 keybounceMBP kernel[0]: hfs: set VeryLowDisk: vol:TimeMachine, backingstore b_avail:78246, tag:16 Feb 23 21:29:33 keybounceMBP KernelEventAgent[136]: tid 54485244 received event(s) VQ_LOWDISK, VQ_VERYLOWDISK (516) Feb 23 21:29:33 keybounceMBP KernelEventAgent[136]: tid 54485244 type 'hfs', mounted on '/Volumes/TimeMachine', from '/dev/disk4s2', low disk, very low disk Feb 23 21:29:34 keybounceMBP mds[131]: (Warning) Volume: Indexing reset and suspended on backup volume "/Volumes/TimeMachine" because it is low on disk space. Feb 23 21:29:36 keybounceMBP com.apple.backupd[26765]: Stopping backup. Feb 23 21:29:36 keybounceMBP com.apple.backupd[26765]: Error: (-34) SrcErr:NO Copying /Volumes/rawKleimanMovies/KleimanMovies.sparsebundle/bands/32c9 to /Volumes/TimeMachine/Backups.backupdb/Keybounce's MacBook Pro/2018-02-23-212008.inProgress/103200FE-3AA8-4766-918F-D60F6A88AAF0/rawKleimanMovies/KleimanMovies.sparsebundle/bands Feb 23 21:32:10 keybounceMBP com.apple.backupd[26765]: Copied 14 items (1.48 GB) from volume rawKleimanMovies. Linked 9498. Feb 23 21:32:10 keybounceMBP com.apple.backupd[26765]: Copy stage failed with error:28 Feb 23 21:32:12 keybounceMBP com.apple.backupd[26765]: Backup failed with error 28: 28 In fact, over the rest of the night and the next morning, the log shows complaints of no space for the indexer, deleting a backup to make room for the indexer, resuming the indexer, and the indexer failing for no disk space. Right now, there is only one backup on the sparse bundle. What do I expect to show in free space? The underlying partition is 3.7 TB. The drive image, if I remember correctly, was made at 3.5 TB. The free space should be 3.5 TB minus the used (one backup). In other words, the space that the disk image claims is available, with a maximum of the actual allocated and unused band space plus the available on the underlying partition. But the other issue is that if someone chooses to not look at free space, and just write, the filesystem should happily reallocate locations in the already allocated band files. The write should succeed. And yes, I also use Backblaze. But I discovered that Backblaze has some serious limitations. It cannot restore file permissions, in particular it does not restore the execute bit. This wrecked all of my shell scripts, for example. I rely on Time Machine for easy access to historical data, such as restoring Firefox browsing history when a Firefox crash results in the places.sqlite file being ruined. Meanwhile: I just used disk utility and explicitly told it to shrink the partition contained inside the sparse bundle file, to a size that I know is small enough to fit on the drive. I'll report if this works. The goal here is to force the file system to rewrite the allocated space in the bands files, and not try to make new bands files. _______________________________________________ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
