ctag
Patron
- Joined
- Jun 16, 2017
- Messages
- 225
Hi,
I'm trying to slim down my iocage jail storage on FreeNAS 11.3-U4.1. One jail in particular takes 240GB of space, despite only having ~12GB of files.
I suspect the issue here is an abundance of snapshots. So I went to SSH and dug around in `zfs list -t snapshot` until I had an idea of what was going on. Right now this system is configured to keep auto-generated snapshots for both 1 and 6 months. But I'm finding snapshots for every dataset going back almost a year, so something seems off.
I found a snapshot before my latest freebsd jail release, and tried removing it and everything earlier:
That.. Didn't seem to work. Apparently iocage uses cloning or something to create the jails, and it's locking me into having all of these snapshots?
If you can help me out of this bind at all, I'd really appreciate it!
I'm trying to slim down my iocage jail storage on FreeNAS 11.3-U4.1. One jail in particular takes 240GB of space, despite only having ~12GB of files.
Code:
root@bns-normandy:~ # df -h Filesystem Size Used Avail Capacity Mounted on main-pool/iocage/jails/bns-normandy/root 18T 12G 18T 0% /
I suspect the issue here is an abundance of snapshots. So I went to SSH and dug around in `zfs list -t snapshot` until I had an idea of what was going on. Right now this system is configured to keep auto-generated snapshots for both 1 and 6 months. But I'm finding snapshots for every dataset going back almost a year, so something seems off.
I found a snapshot before my latest freebsd jail release, and tried removing it and everything earlier:
Code:
# iocage stop ALL # zfs unmount -f tank/iocage # zfs destroy -r main-pool/iocage@%auto-20200617.0900-6m ... would destroy main-pool/iocage/releases/11.2-RELEASE@auto-20200615.0900-6m would destroy main-pool/iocage/releases/11.2-RELEASE@auto-20200616.0900-1m would destroy main-pool/iocage/releases/11.2-RELEASE@auto-20200616.0900-6m would destroy main-pool/iocage/releases/11.2-RELEASE@auto-20200617.0900-1m would destroy main-pool/iocage/releases/11.2-RELEASE@auto-20200617.0900-6m cannot destroy 'main-pool/iocage/releases/11.2-RELEASE/root@bns-normandy': snapshot has dependent clones use '-R' to destroy the following datasets: main-pool/iocage/jails/bns-normandy/root@auto-20200313.0900-6m main-pool/iocage/jails/bns-normandy/root@auto-20200421.0900-6m main-pool/iocage/jails/bns-normandy/root@auto-20200506.0900-6m main-pool/iocage/jails/bns-normandy/root@auto-20200131.1129-1m main-pool/iocage/jails/bns-normandy/root@auto-20200502.0900-6m main-pool/iocage/jails/bns-normandy/root@auto-20200530.0900-1m main-pool/iocage/jails/bns-normandy/root@auto-20200317.0900-6m ...
That.. Didn't seem to work. Apparently iocage uses cloning or something to create the jails, and it's locking me into having all of these snapshots?
If you can help me out of this bind at all, I'd really appreciate it!