Depending on the number of OSTs, I’ve seen some of the big labs use 4 as a default stripe for the filesystem. Other than user education, there’s not much you can do by force. Maybe OST-pools, but that doesn’t prevent someone from hammering a single OST.
docker-compose uptells me that
ERROR: for setup Cannot create container for service setup: invalid mount config for type "bind": bind mount source path does not exist: /tmp/iml_pwwhat the file is for?
iml-node-libzfspackage because it conflicts with my version of nodejs(and if I force its installation, then it fails at runtime). But I stuck on part where
libzfs-sysRust package can't find
libzfs_impl.hjust because it is in
/usr/include. Does anybody know full recipe for cooking this thing? I'm targeting CentOS 7.4.
@AlexTalker In regards for deploying with docker, we’ve intended it to be used with docker stack. Here is a doc for that: