From 68ee2145585539b842eb3251ac7244ad367a6e72 Mon Sep 17 00:00:00 2001 From: Claudio Cambra Date: Mon, 29 Jul 2024 17:28:24 +0800 Subject: [PATCH] Warn admins not to disable file locking when using object storage as primary storage Signed-off-by: Claudio Cambra --- admin_manual/configuration_files/primary_storage.rst | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/admin_manual/configuration_files/primary_storage.rst b/admin_manual/configuration_files/primary_storage.rst index f96d1c4a057..45208dba07e 100644 --- a/admin_manual/configuration_files/primary_storage.rst +++ b/admin_manual/configuration_files/primary_storage.rst @@ -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 ~~~~~~~~~~~~~~~ @@ -258,9 +262,10 @@ 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 `_.