gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Mount Remote Storage (markdown)

Chris Lu 2021-09-01 01:32:15 -07:00
parent a7bc60c99b
commit cc712d8de9
1 changed files with 1 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Mount-Remote-Storage.md

@ -68,11 +68,5 @@ The process is designed to be worry-free. It should automatically resume if stop
Similarly, running `remote.unmount -dir=xxx` can unmount a remote storage. However, this means all cached data and metadata will be deleted. Similarly, running `remote.unmount -dir=xxx` can unmount a remote storage. However, this means all cached data and metadata will be deleted.
And if `weed filer.remote.sync -filer=<filerHost>:<filerPort> -dir=xxx` was not run, the local updates have not been uploaded to the remote storage, so these local updates will be lost. And if `weed filer.remote.sync -filer=<filerHost>:<filerPort> -dir=xxx` was not run, the local updates have not been uploaded to the remote storage, so these local updates will be lost.
Important! When running `remote.unmount -dir=xxx`, the corresponding `weed filer.remote.sync -dir=xxx` should NOT be run. Since the deletion will be propagated to the remote storage! The `weed filer.remote.sync` will stop as soon as it sees the directory is unmounted. So the local deletion will not propagate back to the cloud, avoiding possible data loss.
So the recommended steps to unmount is:
1. Run `weed filer.remote.sync -dir=xxx` to ensure all local updates are persisted to cloud.
2. Stop `weed filer.remote.sync -dir=xxx`
3. Run `remote.unmount -dir=xxx`