What are the limitations of bind mounts? #53
-
Hi! In the documentation, it specifies: So my question is two-fold. Secondly, can we bind datasets? In the example above, it states creating a websites dataset, but then proceeds to bind a subdirectory of that dataset. Does this mean mounting a dataset directly is not recommended? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
It should all be fine. You can essentially mount whatever you want. Just be careful not to mess op the host OS. It should be no problem to mount a dataset directly. |
Beta Was this translation helpful? Give feedback.
-
For TrueNAS to effectively manage it's data it manages datasets with permissions in software for each dataset. There is no write protections on the host OS (located on your boot drive) so if you were to bind /bin, /etc, /var or any of those other host locations with TrueNAS software you risk allowing the jail to overwrite the system files and break your install. You technically CAN bind the pools (groups of drives) but it is highly discouraged due to breaking permissions for any other use of the space in TrueNAS. Correct way is to make a dataset inside the pool and mount that or mount a subdirectory. TLDR: /mnt contains your pools, your pools contain your datasets. Use datasets. If you /mnt or anything above it you risk overwriting TrueNAS files. |
Beta Was this translation helpful? Give feedback.
What would be a bad idea is to mount the /bin directory somewhere in the jail and then remove all files inside it... As long as you mount directories you've made yourself on your own datasets (including the dataset itself) you should be fine.