Dear fellows,
After upgrading to citrine, we had new reports from eos fsck feature that was not there before, and we would like to know how to handle them at best.
These are :
d_mem_sz_diff : most of them are rain files (seem all of the rain files of our namespace, mostly 12 stripes), but they seem sane, they can be read, and are correctly reported by eos file check. What would be the way to remove them from the list, because they might hide replica 2 files which really needs repair. Running eos file verify on rain file silently does nothing, and we once issued a eos fsck repair --resync command which hanged up and we had to restart the MGM (maybe only due to the number of files ?)
rep_missing_n : we never had this error reported with aquamarine version. We understand that some replica are missing, but we have a lot of them (50K). Is it safe to run eos fsck repair --drop-missing-replicas ? Even on 50K files ?
In general, how to handle such reports which contains many many files so that we don’t overload the MGM ?
Thank you
Here is the current content of eos fsck report :
```none
mgm# eos fsck report
timestamp=1521554746 tag="d_cx_diff" n=2 shadow_fsid=
timestamp=1521554746 tag="d_mem_sz_diff" n=588187 shadow_fsid=
timestamp=1521554746 tag="file_offline" n=4 shadow_fsid=
timestamp=1521554746 tag="orphans_n" n=668 shadow_fsid=
timestamp=1521554746 tag="rep_diff_n" n=54 shadow_fsid=
timestamp=1521554746 tag="rep_missing_n" n=45721 shadow_fsid=
timestamp=1521554746 tag="rep_offline" n=0 shadow_fsid=
timestamp=1521554746 tag="unreg_n" n=154 shadow_fsid=
timestamp=1521554746 tag="zero_replica" n=93 shadow_fsid=
