You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent move to docker-ce in stable 3.9.2-3 (#1865) caused the pool hosting the rock-ons-root share to have it's quotas disabled which is not currently a supported configuration within Rockstor. This quotas disabled side affect happens directly after the docker systemd service is activated: often only in evidence after rebooting following the 3.9.2-3 update. The consequent 'quotas disabled' buggy behaviour is to be addressed initially by issue #1869 (further on from now released #1868).
This issue is to address the cause of the quotas disabled state, which appears to be a bug in docker-ce: docker/for-linux#78
which can be partially circumvented by adding an additional option to the dockerd command line as called by our python wrapper script:
/opt/rockstor/scripts/docker_wrapper.py
The noted circumvention is only partial as there is still a momentary disabling of quotas during the dockerd start-up, toward the end of which the quotas are then re-enabled. The consequences of this momentary disabling of quotas is currently under investigation and may require the now almost finalised changes associated with issue #1869 to address. An initial side effect of the current sustained disabled quotas state directly after 3.9.2-3 (post reboot) and before 3.9.2-5 was that all shares hosted by the same pool as the rock-ons-root share were not automatically mounted on boot: this was fixed in 3.9.2-5 by issue #1867 (pr #1868).
Pull request to follow shortly.
The text was updated successfully, but these errors were encountered:
phillxnet
added a commit
to phillxnet/rockstor-core
that referenced
this issue
Dec 17, 2017
It was found that the unwanted and currently unsupported
behaviour of docker-ce disabling quotas, pre this commit,
whenever systemd initiated this dockerd wrapper was
partially circumvented by the addition of the:
btrfs.min_space storage drive option. In this case, although
qoutas were still disabled they were then re-enabled shortly
there after; once the dockerd deamon had settled: returning
the pools quotas to the supported enabled status. Note
however that disabling the docker service still disables
quotas on the associated host pool and the state is persistent.
A recent move to docker-ce in stable 3.9.2-3 (#1865) caused the pool hosting the rock-ons-root share to have it's quotas disabled which is not currently a supported configuration within Rockstor. This quotas disabled side affect happens directly after the docker systemd service is activated: often only in evidence after rebooting following the 3.9.2-3 update. The consequent 'quotas disabled' buggy behaviour is to be addressed initially by issue #1869 (further on from now released #1868).
This issue is to address the cause of the quotas disabled state, which appears to be a bug in docker-ce:
docker/for-linux#78
which can be partially circumvented by adding an additional option to the dockerd command line as called by our python wrapper script:
/opt/rockstor/scripts/docker_wrapper.py
The noted circumvention is only partial as there is still a momentary disabling of quotas during the dockerd start-up, toward the end of which the quotas are then re-enabled. The consequences of this momentary disabling of quotas is currently under investigation and may require the now almost finalised changes associated with issue #1869 to address. An initial side effect of the current sustained disabled quotas state directly after 3.9.2-3 (post reboot) and before 3.9.2-5 was that all shares hosted by the same pool as the rock-ons-root share were not automatically mounted on boot: this was fixed in 3.9.2-5 by issue #1867 (pr #1868).
Pull request to follow shortly.
The text was updated successfully, but these errors were encountered: