Is it a bad idea to nest datasets under the "iocage" dataset?

Joined
Sep 13, 2014
Messages
149
I'd like to create a series of nested datasets to keep the config files from my various Jails. The most logical place to keep said datasets would seam to be nested under the "iocage" dataset along with everything else Jail related.

Is there any reason that this would be a bad idea or is there somewhere better or more sensible that the config datasets should be kept?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
Is there any reason that this would be a bad idea or is there somewhere better or more sensible that the config datasets should be kept?
Yes. Literally anywhere else you want to put them is better.

The redirection to /mnt/iocage from whichever volume is set for jails makes dealing with that dataset in any other way that with iocage problematic, for example when replicating the dataset anywhere, you replicate the mountpoint which can then be selected rather than the intended target to mount at boot if you're replicating to a different pool on the same box.

Just create a jailconfig dataset and put your things there.
 
Joined
Sep 13, 2014
Messages
149
I'm not sure I fully understand your reply.

Do you mean that I could face issues when replicating because the parent "iocage" dataset or it's path would also be replicated and that the system wouldn't know which one to mount and may mount the incorrect one?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
The replica will have the same mountpoint as the original, since it's not unique to the pool on the original side, so it's a crapshoot as to which will be mounted on boot.
 
Joined
Sep 13, 2014
Messages
149
[EDIT] I'll probably nest the dataset somewhere else, to avoid any future issues but still, I'm just wondering whether it will actually be an issue for me though, as the only replication I ever do is either to my secondary backup system or when I'm duplicating a dataset to the same pool / system with the intention of deleting the original dataset (which I only do once in a blue moon).

I am considering adding another pool to my primary server, solely for Jails, Plugins and perhaps the odd VM. That's the most likely scenario of if I were to replicate a dataset to the same system. But as I said above, once the Jails / iocage dataset was replicated to the new pool, the original would be deleted or at the very least, have it's mount point moved or renamed using `zfs rename`.
 
Last edited:

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
I don't see the problem with making another dataset in an existing pool either, but you can do it as you please with the awareness that if you replicate, you need to think carefully.
 
Top