This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Recovered Repository Space

I had extended the retention policy on my core but found myself running out of space after a few unexpected base images were made. I set the policy back to the default and after the next rollup job it looked like it removed extra snapshots but I have not gained any space back. I suspect I have but it just does not show on the console.

Do I need to reboot or will it just catch up eventually?

Parents
  • In the events tab of the core console enable the services filter (it's a gear icon). When you do that see if there are "Deleting Index RPFS Files" jobs running. If there are, that is the background deferred delete process actually deleting data from the repository. Rollup marks the data for deletion, "deleting index RPFS files" actually deletes the data and reclaims the space. If there are no jobs running, then I recommend restarting the core service and checking to see if they start. If they still don't, I'd contact support and have them dig into the issue further.

  • I do not see any jobs running but I did notice a little more space was recovered. It is currently snapshotting a server but I will restart it after and see what happens.

    It seems to me I ran into this a while ago and it did eventually creep back but it took a while

    Thanks.

  • Is there a Deleting Index RPFS Files job that has ran and completed AFTER the change was made and after rollup has ran? We have seen several cores where jobs are not running, so if rollup has not ran or the delete has not ran, space wont be reclaimed. 

    We are also seeing cores not reclaiming space at all, so there are a lot of issues. But since none of the jobs track repo space, you cant prove anything you say. We are having this issue with an optimization job that is eating up repo space but we cant prove it in the logs

  • I saw no RPFS job at all in the events log but I have not given up hope. Like I said I'm pretty sure I had this problem before and it did sort itself out eventually.

    As of late I have considered encrypting everything which would require me to take all new base images so if it gives me too much grief I will wipe out the repository and start over. We are a relatively small environment and my whole repo is only 6TB. It sucks but it's not the end of the world but I can see how it would be an issue.

  • If there is no RPFS job, then you have an issue. I assume the problem is with the funky events display. Make sure you are seeing service jobs (the gear icon)

  • My mistake there are/were several RPFS jobs and one running now. I am still slowly seeing space recovered so I am going to assume it is working.

    For anyone that finds this in the future you need to first open the events window (heartbeat icon upper left of console between "virtual standby" icon and "settings" icon). Then you need to click on the gear icon in the upper right of the tasks window to show "service jobs" as they are HIDDEN otherwise.

Reply
  • My mistake there are/were several RPFS jobs and one running now. I am still slowly seeing space recovered so I am going to assume it is working.

    For anyone that finds this in the future you need to first open the events window (heartbeat icon upper left of console between "virtual standby" icon and "settings" icon). Then you need to click on the gear icon in the upper right of the tasks window to show "service jobs" as they are HIDDEN otherwise.

Children
No Data