[GH-ISSUE #1417] Human error inadvertently clobbering s3fs-fuse meta and/or data? #750

Closed
opened 2026-03-04 01:48:27 +03:00 by kerem · 1 comment
Owner

Originally created by @socomsystems on GitHub (Sep 21, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1417

Case scenario:

  • First bucket named XYZ with s3 like provider A. This bucket's mount maps to: /var/s3-storage/client/rodman

  • Second bucket named XYZ with s3 like provider B. This bucket's mount maps to: /var/s3-storage/client/rodwoman

  • A Nextcloud or Owncloud module that facilitate access to s3 like "external storage" instances is created as type "local" dir /home/rodman/storage mapping to /var/s3-storage/client/rodman

  • Four separate computers storage volumes have mirrors of the /home/rodman/storage directory and replicate via torrent app SyncThing.

Mounts execute successfully, can anyone shred some light on what happens to the meta or other issues arising from this case?

This case happened, nothing stopped it from happening and things went a foul - will post more info as soon as I can. Posting to Github issues for Nextcloud, Owncloud and Syncthing as well.

Cheers,
Troy

Originally created by @socomsystems on GitHub (Sep 21, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1417 Case scenario: - First **bucket named XYZ** with s3 like **provider A.** This bucket's mount maps to: /var/s3-storage/**client/rodman** - Second **bucket named XYZ** with s3 like **provider B**. This bucket's mount maps to: /var/s3-storage/**client/rodwoman** - A Nextcloud or Owncloud module that facilitate access to s3 like "external storage" instances is created as type "local" dir /home/rodman/storage mapping to /var/s3-storage/**client/rodman** - Four separate computers storage volumes have mirrors of the /home/rodman/storage directory and replicate via torrent app SyncThing. **_Mounts execute successfully, can anyone shred some light on what happens to the meta or other issues arising from this case?_** This case happened, nothing stopped it from happening and things went a foul - will post more info as soon as I can. Posting to Github issues for Nextcloud, Owncloud and Syncthing as well. Cheers, Troy
kerem 2026-03-04 01:48:27 +03:00
  • closed this issue
  • added the
    need info
    label
Author
Owner

@gaul commented on GitHub (Oct 6, 2020):

Sorry I cannot parse this issue. Please reopen if you have a more specific s3fs query.

<!-- gh-comment-id:703987907 --> @gaul commented on GitHub (Oct 6, 2020): Sorry I cannot parse this issue. Please reopen if you have a more specific s3fs query.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#750
No description provided.