mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-26 05:45:57 +03:00
[GH-ISSUE #1417] Human error inadvertently clobbering s3fs-fuse meta and/or data? #750
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#750
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@gaul commented on GitHub (Oct 6, 2020):
Sorry I cannot parse this issue. Please reopen if you have a more specific s3fs query.