From efd12875f0765200d9a3fc5509620572b579066a Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Tue, 31 Aug 2021 02:22:29 -0700 Subject: [PATCH] Updated Mount Remote Storage (markdown) --- Mount-Remote-Storage.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Mount-Remote-Storage.md b/Mount-Remote-Storage.md index dab698b..962d672 100644 --- a/Mount-Remote-Storage.md +++ b/Mount-Remote-Storage.md @@ -65,6 +65,14 @@ The process is designed to be worry-free. It should automatically resume if stop ## Unmount a Remote Storage -Similarly, running `remote.unmount -dir=xxx` can unmount a remote storage. However, this means all cached data and metadata will be lost. +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=: -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! + +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` + +