Hi,
I have a few jails running on a new server. This works really well and I'm quite happy with the whole setup. Jails are a very powerfull tool, that much is clear. However, there is one jail that gives me an annoying problem.
I use ezjail-admin to manage all my jails and I like the tool a lot. I installed all the jails in the standard /usr/jails directory with all the power of ZFS that ezjail-admin provides (on the standard zroot, that the FreeBSD installation wizard provides). All jails, except for one. And that one jail is giving me problems.
That jail is running a webserver, that hosts Nextcloud. I needed more than usual storage for this setup, so I put it on a seperate ZFS-pool, with larger drives.
The problem is that when I reboot the (physical) server, something goes wrong when mounting that ZFS-partition. For some reason it gets mounted correct and than it gets mounted again a second time, with an empty partition or something. That causes the partition where the jail is stored appear to be empty. And that gives me a jail that doesn't start.
The remedy to this problem is easy. I simply do an umount on that partition.
This makes all the files magically re-appear again and now I can start the jail without any problems. So it itsn't a big issue perse. It's just really annoying. And it could become a problem when someone else, who doesn't know about this, needs to do a reboot. It's just sloppy. And it bugs me.
Any advice on how to make this work smooth?
Thanks in advance
I have a few jails running on a new server. This works really well and I'm quite happy with the whole setup. Jails are a very powerfull tool, that much is clear. However, there is one jail that gives me an annoying problem.
I use ezjail-admin to manage all my jails and I like the tool a lot. I installed all the jails in the standard /usr/jails directory with all the power of ZFS that ezjail-admin provides (on the standard zroot, that the FreeBSD installation wizard provides). All jails, except for one. And that one jail is giving me problems.
That jail is running a webserver, that hosts Nextcloud. I needed more than usual storage for this setup, so I put it on a seperate ZFS-pool, with larger drives.
ezjail-admin create -r /Storage/jails/nextcloud.jail nextcloud.jail 123.123.123.123The problem is that when I reboot the (physical) server, something goes wrong when mounting that ZFS-partition. For some reason it gets mounted correct and than it gets mounted again a second time, with an empty partition or something. That causes the partition where the jail is stored appear to be empty. And that gives me a jail that doesn't start.
The remedy to this problem is easy. I simply do an umount on that partition.
umount /Storage/jails/nextcloud.jailThis makes all the files magically re-appear again and now I can start the jail without any problems. So it itsn't a big issue perse. It's just really annoying. And it could become a problem when someone else, who doesn't know about this, needs to do a reboot. It's just sloppy. And it bugs me.
Any advice on how to make this work smooth?
Thanks in advance
