Daisuke
Contributor
- Joined
- Jun 23, 2011
- Messages
- 1,041
In simple terms, "hostPath validation" setting prevents the use of same pool dataset for both apps and shares. From my understanding, there are a lot of apps changing file permissions without any warnings, or they simply don't work with share ACLs. That's the main reason why you should not disable that setting and instead, organize your datasets properly (edit: I'm going to add this info into guide). I'll invite @morganL and @Kris Moore to add more specific details.why it's bad to disable the hostPath safety checks?
I spent quite a lot of time writing clear instructions how to properly organize your datasets, it will be very beneficial for future upgrades. Just following the Linux standard naming conventions when you organize your datasets will automatically solve all your hostPath validation issues. Follow my guide suggestions and you will not be dissapointed. In the long term, things will be so much easier when you will create new datasets.
If you plan to organize your datasets, create new ones and make sure you look at
recordsize
related information, posted into Pools and Datasets section. It is quite important, many people have no idea how much this setting can impact their system performance, when it comes to read/write speed and latency.Honestly, the scripts are for someone with Linux knowledge, since Scale is a Linux Debian based OS. So, yes, there is a small learning curve required. I'll add more details how to execute the scripts, thank you for the input.I am also a newbie and don't have a clue how to run your scripts as instructed.
Edit: I added the Linux Terminal Conventions section, which also demonstrates how to login into your Scale server with
ssh
.
Last edited: