Skip to content

Warn admins not to disable file locking when using object storage as primary storage #12073

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.

Sign up for GitHub

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

Draft
claucambra wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Warn admins not to disable file locking when using object storage as primary storage #12073

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 8 additions & 3 deletions admin_manual/configuration_files/primary_storage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,10 @@ The configuration has the following structure:
],
],

.. note:: You are NOT supposed to disable file locking and this is now considered potentially
dangerous. Locking is handled in Redis and is handled separately from the underlying storage. If
you have disabled file locking already it is highly encouraged for you to re-enable it.

~~~~~~~~~~~~~~~
OpenStack Swift
~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -264,9 +268,10 @@ configuration in :code:`config.php`:
Multibucket object store backend maps every user to a range of buckets and saves
all files for that user in their corresponding bucket.

.. note:: While it is possible to change the number of buckets used by an existing Nextcloud
instance, the user-to-buckets mapping is only created once, so only newly created
users will be mapped to the updated range of buckets.
.. note::
While it is possible to change the number of buckets used by an existing Nextcloud
instance, the user-to-buckets mapping is only created once, so only newly created
users will be mapped to the updated range of buckets.

You can find out more information about upscaling with object storage and Nextcloud in the
`Nextcloud customer portal <https://portal.nextcloud.com/article/object-store-as-primary-storage-16.html>`_.
Expand Down