Skip to content

DLPX-65491 Invalid argument when mounting ZFS filesystem #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 31, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions files/common/lib/sysctl.d/50-override.conf
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,19 @@ net.ipv4.tcp_rmem = 4096 4194304 16777216
# allows the script that generates the hprof dump to run.
#
vm.overcommit_memory = 1

#
# By default all mounts are "shared" with other mount peer groups.
# As a results any new mount will propagate the mount event to other
# mount namespaces that is part of that peer group. This means that the
# counts associated with a mount namespace may be higher than the number
# of actual mounts in the initial namespace. We have observed that
# systemd-resolved and systemd-networkd have twice the number of mounts
# compared to the initial mount namespace. Additionally, as we create
# containers systemd-resolved and systemd-networkd will add the mounts
# from the initial namespace again. This can lead to an inflation of
# 3 times what is actually mounted. In order to be able to support
# 100,000 filesystems in the initial namespace the maximum number of
# mounts allowed by the system must be 3 times the supported value.
#
fs.mount-max = 300000