diff options
| author | Christian Pointner <equinox@spreadspace.org> | 2020-05-26 23:50:38 +0200 |
|---|---|---|
| committer | Christian Pointner <equinox@spreadspace.org> | 2020-05-26 23:50:38 +0200 |
| commit | acc437083cfa7b8f77b8e79af2a0c05bd871e198 (patch) | |
| tree | 576360023addac147bef43f1ba340c61e3c9fe5b /roles/kubernetes | |
| parent | remove nextcloud test instance (diff) | |
| parent | cleanup old configs and playbooks (diff) | |
Merge branch 'topic/zfs-buster-backports'
Diffstat (limited to 'roles/kubernetes')
| -rw-r--r-- | roles/kubernetes/base/tasks/zfs.yml | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/roles/kubernetes/base/tasks/zfs.yml b/roles/kubernetes/base/tasks/zfs.yml index c417a1b6..4311dd3f 100644 --- a/roles/kubernetes/base/tasks/zfs.yml +++ b/roles/kubernetes/base/tasks/zfs.yml @@ -13,9 +13,3 @@ fstype: none opts: bind,x-systemd.automount,nofail state: mounted - -## TODO: -## there is a race condition between the bind mound and the zfs-mount which is invisible to systemd. -## It seems ZFSonLinux 8 and beyond have a systemd-generator to fix this problem. Sadly Debain Buster and Ubuntu Bionic contain -## ZFSOnLinux 7 - so let's try the folllowing for a possible workaround: -## https://askubuntu.com/questions/988968/which-zfs-command-systemd-unit-to-depend-on-to-ensure-that-a-mountpoint-is-avail |