"Jail dataset created on a share"

[greenamex2]

Hi all

I now get this message "Jail dataset created on a share" when I select "Jails -> Configuration -> Save", without having actually having changed anything.

The Jails are located on - /mnt/Internal/jails.

I DID have a CIFS share mounted from /mnt/Internal but I have now deleted this. There are a number of shares mounted on folders below /mnt/Internal.

I am on build "FreeNAS-9.10.1-U3 (d985cd1)".

Any ideas?

Thanks

 

[kuruption]

Same here... seeing this error. No shares under that directory (or its parents).

 

[dlavigne]

That sounds related to this fix: https://bugs.freenas.org/issues/15705. Please create a bug report at bugs.freenas.org indicating that it should only trigger a warning when you actually try to create a jail on top of an existing dataset and post the issue number here.

 

[mysticpete]

Yeah.... err this isn't fixed, just discovered it still on Build FreeNAS-9.10.2-U3 (e1497f269)

 

[isometry]

For the benefit of others, it looks like this bug can be triggered by having an SMB "home" share configured with an empty path.
Workaround: set a non-empty path for your SMB home share (e.g. the parent directory of your home shares).

 

[fracai]

I was just hit by this (9.10.1-U4 with one AFP share from the root of my pool) and was able to workaround it by disabling AFP and temporarily changing the shared path (/mnt/pool to /mnt/pool/foo; my jails are at /mnt/pool/jails). After I saved my changes I set the AFP share back to it's original state.

 

[genBTC]

This thread is the first result on google. So
What worked for me:

• Make it so the jail path cannot be visible by any of your CIFS/SMB/AFP/NFS shares.

ie:
If /mnt/MyPool is shared on SMB , and you try to create a jail at /mnt/MyPool/jails - it will fail with this error.
What you do is set the SMB to share from /mnt/MyPool/shared, (AND RESTART SAMBA) and then the jail will install correctly in for /mnt/MyPool/Jails
After the jail works, you can go back and set your SMB share to /mnt/MyPool/ again if you really wanted to, but...
This error is a hard warning to NOT do that, because then all the jail data will become visible over the Shares.

 

[emk2203]

@genBTC: You might want to add NFS shares to your list, since these trigger the error as well.

 

[danb35]

This error is a hard warning to NOT do that, because then all the jail data will become visible over the Shares.

...and also because there's a greatly increased risk that you'll inadvertently change permissions on your jails dataset, borking all your jails. The warning is there for very good reasons.

 

[AnsisMalins]

Hello. I'm stupid. What's wrong with creating a jail dataset on a share? Also, the message is there to warn me, and FreeNAS does not actually stop me from doing it, correct?

 

[danb35]

What's wrong with creating a jail dataset on a share?

The message right above yours gives at least one good reason.

FreeNAS does not actually stop me from doing it, correct?

No, that isn't correct; FreeNAS does prevent you from doing this.