Skip to content

[stable-35.0] revert: unique inode index - #11182

Merged
nilsding merged 3 commits into
stable-35.0from
backport/11179/stable-35.0
Oct 30, 2026
Merged

nilsding merged 3 commits into
stable-35.0from
backport/11179/stable-35.0

Conversation

@backportbot

@backportbot backportbot Bot commented Oct 30, 2026

Copy link
Copy Markdown

Backport of PR #11179

This reverts commit 4c820c5,
reversing changes made to 1503e53.

Assisted-by: Codex:GPT-6
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
This reverts commit 42ed001,
reversing changes made to af03b85.

Assisted-by: Codex:GPT-6
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
Drop metadata_unique_inode when opening journals so existing databases
no longer enforce the reverted inode uniqueness constraint. Reset the
version query before schema updates to release its read lock.

Add regression coverage for existing and absent indexes, metadata
preservation, duplicate and zero inode writes, and repeated reopening.

Assisted-by: Codex:GPT-6
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
@nilsding
nilsding merged commit 0776141 into stable-35.0 Oct 30, 2026
20 of 23 checks passed
@nilsding
nilsding deleted the backport/11179/stable-35.0 branch October 30, 2026 14:28
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