nextcloud / nextcloud/server

[Bug]: Syncing to S3 Storage (e.g. minio server) syncs folders twice into a subtree

Open
#42,336 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 27-feedback bug feature: external storage feature: object storage needs review
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

look below

Steps to reproduce

1.Minio S3 Storage provide a bucket
2. Syncing to bucket with NExtcloud 27 syncs folders twice into a subtree
3. means /example plus content of folder syncs to /example plus content of folder AND /example/example plus content of folder
4. you see the bug only on the S3 storage side, not within Nextcloud !
5. pydio client e.g. does not make this bug in S3 structure, so it is a bug of nextcloud

Expected behavior

syncs only once with mirroring exactly the folder structure

Installation method

Community Docker image

Nextcloud Server version

27

Operating system

Debian/Ubuntu

PHP engine version

None

Web server

Nginx

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with Nextcloud 27 and a Minio S3 bucket, then compare the bucket tree with the original folder structure. The issue provides no file or test entry point; done means each folder and its contents appear only once in the S3-side mirror.

Written by the indexing model from the issue text.

Assessment

Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.