Skip to content

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

Merged
skjnldsv merged 3 commits into
masterfrom
bugfix/file-locking-s3
Nov 19, 2026
Merged

skjnldsv merged 3 commits into
masterfrom
bugfix/file-locking-s3

Conversation

@claucambra

Copy link
Copy Markdown
Contributor

☑️ Resolves

Multiple admins, due to advice on the internet (e.g. https://autoize.com/s3-compatible-storage-for-nextcloud/), have disabled file locking when using object storage as primary storage. This note warns them not to do so

@claucambra claucambra self-assigned this Jul 29, 2024
@claucambra
claucambra force-pushed the bugfix/file-locking-s3 branch from dff388f to 68ee214 Compare July 29, 2024 09:46
@nextcloud nextcloud deleted a comment from github-actions Bot Aug 8, 2025
@skjnldsv

Copy link
Copy Markdown
Member

@claucambra what's the status here? Could you update the labels please

…primary storage

Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
@skjnldsv
skjnldsv force-pushed the bugfix/file-locking-s3 branch from 68ee214 to f2b81ae Compare April 20, 2026 17:05
@skjnldsv
skjnldsv marked this pull request as draft April 20, 2026 17:05
Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

Last updated: Thu, 19 Nov 2026 05:16:13 GMT

@skjnldsv
skjnldsv marked this pull request as ready for review November 19, 2026 05:03
Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
@skjnldsv
skjnldsv merged commit b609b6c into master Nov 19, 2026
27 checks passed
@skjnldsv
skjnldsv deleted the bugfix/file-locking-s3 branch November 19, 2026 05:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants