amkassir Posted July 14, 2015 Report Share Posted July 14, 2015 After completing a groom operation, the log shows: Executing Groom OWC at 7/14/15, 12:27:00 PM Grooming Media Set OWC Backup... Groomed 29.9 GB from Media Set OWC Backup. 7/14/15 1:12:00 PM: Execution completed successfully Completed: 52,074 files, 29.9 GB Performance: 681.7 MB/minute Duration: 00:44:58 It looks like 29.9GB was groomed. Inspection of the media set under Media Sets shows: Used: 276.1 GB Free: 14.4 GB Capacity: 322 GB I would expect the free amount to match or exceed the amount groomed (29.9 GB) but it is less. Also, the capacity minus the used amount is 45.9 GB. Shouldn't that amount match the free amount? Retrospect 12.0.2 Yosemite Backing up to external firewire disk Thanks in advance for your help. 2 Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 15, 2015 Report Share Posted July 15, 2015 14.4 + 29.9 = 44.3 GB. 322 - 276.1 = 45.9 GB. Not much difference. Is this a coincidence or is it rounding errors that makes the slight difference? In Finder, perform a "Get Info" on the media set folder. How much is used? Does Retrospect display in GiB or GB? I think Finder uses GB nowadays. https://en.wikipedia.org/wiki/Gibibyte Quote Link to comment Share on other sites More sharing options...
amkassir Posted July 15, 2015 Author Report Share Posted July 15, 2015 Hello Lennart: Thanks for your post. The problem was that Retrospect reported less free space in the Media Set (14.4 GB) than should have been free after grooming (45.9 GB, or 44.3 if you prefer). Incidentally, after ejecting the volume and then remounting it, and restarting the Retrospect console, the free space was updated in the Retrospect console to the correct value, 45.9 GB. I think this represents a bug or a limitation of Retrospect. Ideally it would update to show the correct free space in the Media Sets view after a grooming operation. Restarting the Retrospect console was not sufficient to update the value. I also resized the volume from 95% used, to 99% used, and then back to 95% used, before I noticed the free space was correctly reported, so it's possible the resizing triggered the update. I didn't check the free space value before resizing. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 15, 2015 Report Share Posted July 15, 2015 It looks like a screen update bug to me. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.