Two Tanks: Plugins only start up after reboot on one Tank

[Dellyjoe]

Hello everyone,

When I made my Truenas core setup about 1 year and 6 months ago, I used two Tanks. One for X and the other for Y data. I did this so I could keep data from X completely separate from data Y.

However this has become a pain when you have plugins installed on each Tank. If I select Tank 1 and reboot the Truenas sever Tank1's plugs will start up after reboot. Then I have to switch to the other Tank to then manually start up those Plugins.


Does anyone know how to create a cron job to start up the non-select Tank plugins after reboot? Or start up the plugin after reboot even if the current selected Tank isn't selected?

Thank you in advanced,
Joe

 

[Samuel Tai]

You're fighting against iocage's design assumption of only a single pool being used for jails/plugins. Having 2 pools whose root datasets both have the org.freebsd.ioc:active=yes property leads to undefined iocage behavior.

 

[sretalla]

To elaborate that a bit more...

Data shouldn't live in jails.

If you want data in a jail, you mount it in there from your pool/dataset location.

You could have your jails on either of those pools (or on a different one) and mount data in only to the jails you want separately, which keeps any one jail from seeing data on the pool you don't want it to.

 

[Dellyjoe]

You're fighting against iocage's design assumption of only a single pool being used for jails/plugins. Having 2 pools whose root datasets both have the org.freebsd.ioc:active=yes property leads to undefined iocage behavior.

Thank you for relaying Samuel: Understood when I started my freenas server journey I didn't know anything about servers. With the information I have learned over the year I would go with one bigger pool then two smaller ones.

Is there a way to combined the pools now? I thinking not.

To elaborate that a bit more...

Data shouldn't live in jails.

If you want data in a jail, you mount it in there from your pool/dataset location.

You could have your jails on either of those pools (or on a different one) and mount data in only to the jails you want separately, which keeps any one jail from seeing data on the pool you don't want it to.

Thank you for the relay stetalla, I believe I do this. My jails only have access to data they need to have access to, which I use the mount link to provide that jail with its data.


So I'm guessing there isn't a way to start up a pools plugins/jails from the non-primary pool?

Thank you for the relay in advanced,
Joe

 

[sretalla]

So I'm guessing there isn't a way to start up a pools plugins/jails from the non-primary pool?

The jail itself can only live in the jails dataset (there can only be one in use on any given system and being a dataset, can be only on one pool at any time).

Jails themselves and their root filesystems should be more-or-less disposable and would contain no secret or important data, so it shouldn't really matter where they reside from a security/access perspective.

 

[Dellyjoe]

The jail itself can only live in the jails dataset (there can only be one in use on any given system and being a dataset, can be only on one pool at any time).

Jails themselves and their root filesystems should be more-or-less disposable and would contain no secret or important data, so it shouldn't really matter where they reside from a security/access perspective.

Thank you for your response Stetalla, I understood what you are saying. wish I didn't make two pools from the beginning. When I upgrade my sever in a couple of years I will make sure to move to one pool !

Thank you for your time,
Joe