From 6bf80daf66d079745e036a25ed5107293764e65b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rn=20Friedrich=20Dreyer?= Date: Tue, 14 Sep 2021 09:51:23 +0200 Subject: [PATCH] explain sharding relationship with deprovisioning --- docs/ocis/storage-backends/cephfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ocis/storage-backends/cephfs.md b/docs/ocis/storage-backends/cephfs.md index b0859ea1c4..fa3de4357d 100644 --- a/docs/ocis/storage-backends/cephfs.md +++ b/docs/ocis/storage-backends/cephfs.md @@ -52,7 +52,7 @@ Shares [are be mapped to ACLs](https://github.com/cs3org/reva/pull/1209/files#di - If needed for redundancy, the share manager can be run multiple times, backed by the same cephfs - To save disk io the data can be cached in memory, and invalidated using stat requests. - A good tradeoff would be a folder for each user with a json file for each list. That way, we only have to open and read a single file when the user want's to list the shares. -- To allow deprovisioning a user the data should by sharded by userid. +- To allow deprovisioning a user the data should by sharded by userid. That way all share information belonging to a user can easily be removed from the system. If necessary it can also be restored easily by copying the user specific folder back in place. - For consistency over metadata any file blob data, backups can be done using snapshots. - An example where einstein has shared a file with marie would look like this on disk: ```