From d5bee44718b401d2944bfad4e3b37416d6caf427 Mon Sep 17 00:00:00 2001 From: srijan-sivakumar Date: Wed, 7 Apr 2021 20:20:49 +0530 Subject: [PATCH] Adding limitation in glusterfind. Currently the glusterfind operation is disrupted if even one node is down during the pre. This is due to the fact that changelogs are required to be captured from the specific bricks and then aggregated. Fixes: #677 Signed-off-by: srijan-sivakumar --- docs/GlusterFS-Tools/glusterfind.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/GlusterFS-Tools/glusterfind.md b/docs/GlusterFS-Tools/glusterfind.md index 442b3f4a..29764cf0 100644 --- a/docs/GlusterFS-Tools/glusterfind.md +++ b/docs/GlusterFS-Tools/glusterfind.md @@ -181,3 +181,4 @@ Where `START_TIME` is in unix epoch format, `START_TIME` will be zero for full f 1. Deleted files will not get listed, since we can't convert GFID to Path if file/dir is deleted. 2. Only new name will get listed if Renamed. 3. All hardlinks will get listed. +4. All the nodes are to be up and running for the successful operation of glusterfind.