Tidying up after an upgrade

[adrianwi]

I've just upgraded to 13.0-U1 and upgraded most of the iocage jails to use the 13.1 template.

I was doing some tidying and noticed the downloads and release folders. Is it safe to remove the older 11x and 12x if they are not being used by any jails? I still have a couple on 12.2-p2 so will leave that one and the current 13.1 alone.


Thanks

 

[winnielinnie]

I destroyed all the datasets underneath download after upgrading all my jails to 13.1-RELEASE.

I destroyed everything but 13.1-RELEASE underneath releases, since all of my jails are now exclusively on 13.1-RELEASE.

Just be careful when destroying datasets, and go slowly. Keep in mind, this assumes you won't be rolling back any jails to previous releases.

 

[adrianwi]

Thanks.

I gave this a whirl last night and noticed that whenever I deleted a dataset from the iocage/download or iocage/release folders, it takes down my running jails, and I have to restart them all again. Not a big issue, but was wondering if this was the default operation and why does it need to do this?

 

[Patrick M. Hausen]

Did you do this in the UI? I have done this on the CLI dozens of times without that issue.

 

[winnielinnie]

whenever I deleted a dataset from the iocage/download or iocage/release folders, it takes down my running jails, and I have to restart them all again.

Did you do this in the UI? I have done this on the CLI dozens of times without that issue.

When I first did it, I stopped my jails manually after finishing the upgrade process, and I did not start them up again until I finished tidying up.


So based on what you shared, I just did a test using the GUI.

I fetched 13.0-RELEASE (as a test). Then I destroyed the dataset pool/iocage/downloads/13.0-RELEASE

Guess what? All my jails were automatically stopped, and I had to manually restart them.

So maybe doing it via the GUI triggers something to stop the running jails?


UPDATE: As an additional test, for the sake of it with TrueNAS Core 13.0-U1.1, I wanted to see if this also occurs for any dataset. I created a a new "sample" dataset and then deleted it, but this did not stop my jails.


However, when I repeated the first test above, it once again stops all of my jails.

Deleting either of these two datasets will trigger this issue:

• dataset pool/iocage/downloads/13.0-RELEASE
• dataset pool/iocage/releases/13.0-RELEASE

This might hint to the fact that something in the middleware is watching for the removal of particular datasets under that iocage dataset, which will trigger a "stop" to your jails?