Login
You're viewing the functional.cafe public feed.
  • Nov 7, 2026, 5:20 PM

    @dvl I use them in jail provisioning:

    $ zfs list -t snapshot zroot/jails/templates/15.1-RELEASE-amd64-amd64
    NAME USED AVAIL REFER MOUNTPOINT
    zroot/jails/templates/15.1-RELEASE-amd64-amd64@unpacked 120K - 350M -
    zroot/jails/templates/15.1-RELEASE-amd64-amd64@verified 132K - 350M -
    zroot/jails/templates/15.1-RELEASE-amd64-amd64@tweaked 0B - 611M -
    zroot/jails/templates/15.1-RELEASE-amd64-amd64@ready 0B - 611M -

    but the trick is that the ansible scripts check for the *directory* /jails/templates/15.1-RELEASE-amd64-amd64/.zfs/snapshot/ready/ to decide if they can skip a phase.

    It makes the provisioning a lot faster, as mostly there's no work to be done, and avoids needing to shell out to a zfs command each time.

    To patch the jails, I just rollback or destroy the templates, re-run ansible and everything is populated.

    💬 1🔄 0⭐ 0

Replies

  • Nov 9, 2026, 9:17 PM

    @dch I think I get it.

    You never update jails, they get redeployed. I don't have that setup. I do have ansible playbooks for some thing, but not a set-up-from-nothing script.

    💬 1🔄 0⭐ 0
  • Nov 9, 2026, 9:29 PM

    @dvl yea this. Once I learned how to split off mutable / backup-required data from pkg / os files, this got a lot simpler. With container this is getting even easier.

    💬 0🔄 0⭐ 0