rangopango
Contributor
- Joined
- Feb 21, 2018
- Messages
- 151
I don't have a spare volume to put it on, so how do I temporarily disable it or whatever. It keeps automatically adding itself to my current volume and I don't want it to do that.

I don't have a spare volume to put it on, so how do I temporarily disable it or whatever. It keeps automatically adding itself to my current volume and I don't want it to do that.
~ # zfs list -o space volume0/jails NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD volume0/jails 1.28T 88K 0 88K 0 0
Why not? It has to go somewhere if you're going to have jails--and there's no reason for it to not be on your main pool.I don't want it to do that.
I don’t understand, if you don’t have any jails there shouldn’t be a jails dir.I suppose there is no solution
I don't understand what you mean. The system allows you to define the root for jails on any data volume you have available. It takes a negligible amount of space and no resources if you don't define any jails. Of course, if you have only one data volume, then that is where the root dataset goes.i don't have a choice to define a root for jails, it automatically creates one in any volume where I don't want it, that is the problem
No, it doesn't. If/when you create a jail, the template is downloaded at that time. But there's no reason that a jails dataset must exist on a base installation.A FreeNAS installation includes some jail templates,
It doesn't.I don't understand why it has to be there
How do i get rid of it, I'm not using jails anyway (but I might in the future, who knows)
What does this mean?
freenas.local changes in mounted filesystems:
13d12
< Volume/jails /mnt/Volume/jails zfs rw,noatime,nfsv4acls 0 0
-- End of security output --
Volume/jails
dataset was mounted to /mnt/Volume/jails
while at the current boot this dataset isn't mounted. Hmm, did you finally reach your goal to get rid of a jail root dataset? Is the output of mount | grep jails
empty?