Looking at our SyncIQ policies, the following 2 settings seem to be the key:
Report Max Age: 4W2D
Report Max Count: 2000
So, the age policy isn't overriding the count policy, and we end up with 2000 SyncIQ reports per policy, e.g.:
# ls /ifs/.ifsvar/modules/tsm/sched/reports/0007430a77cc3fc78755150883d43aa1|wc -l
# du -sh /ifs/.ifsvar/modules/tsm/sched/reports/0007430a77cc3fc78755150883d43aa1
There are a few options for reducing the size of log gathers. We detail them below.
OneFS 126.96.36.199 offers the ability to exclude node reboot cores, process cores, and hangdumps when running isi gather info. When running isi_gather_info, add one or both of these switches to the command to limit what is gathered:
OneFS 188.8.131.52 offers the ability to clean node reboot cores, process cores, and hangdumps after they have been gathered with isi_gather_info. When running isi_gather_info, add this switch to the command to clean those cores and hangdumps from the cluster:
If you wish to clean only cores, or only hangdumps, you can add one of the following switches to the isi_gather_info command:
When a node reboots, it creates a file in /var/crash with a filename that starts with vmcore. If those vmcore files have already been uploaded to EMC support for analysis, you can remove the file(s) with this command:
isi_for_array "rm -rf /var/crash/vmcore*"
During file locking activity, the isi_hangdump daemon will sometimes trigger a hangdump on all nodes in the cluster which creates a diagnostic file in /var/crash with a filename that starts with isi_hangdump. If those hangdump files have already been uploaded to EMC support for analysis, you can remove the file(s) with this command:
isi_for_array "rm -rf /var/crash/isi_hangdump*"
When a process terminates abnormally, it usually writes out the contents of its memory into a core file and stores that file in /var/crash with a filename that ends with .core.gz. If those core files have already been uploaded to EMC support for analysis, you can remove the file(s) with this command:
isi_for_array "rm -rf /var/crash/*.core.gz"
During isi_vopy_copy or isi_vol_copy_vnx migrations, those processes create files in /ifs/.ifsvar/tmp that begin with the filename rst. If you do not need those files any longer, you can remove them from that directory with this command:
rm -rf /ifs/.ifsvar/tmp/rst*
OneFS 184.108.40.206 had a problem with its isi_gather_info script which would cause the FSAnalyze reports databases to be collected, driving up the size of the log gather. This issue was resolved in OneFS 220.127.116.11.
SyncIQ report files can take up larger than expected amounts of space and possibly increase the amount of time it takes isi_gather_info to complete its log gather. You can adjust the amount of SyncIQ report retention to keep only a certain number of reports, or limit how long it will keep reports via these command line options. Choose which command suits your needs best and apply it to existing policies.
isi sync policies modify <policy> --report-max-age <duration>isi sync policies modify <policy> --report-max-count <count>
Once you have made this change to your policies you can change the defaults for new policies with the following commands:
isi sync settings modify --report-max-age <duration>
isi sync settings modify --report-max-count <count>
Please let us know if you have any other questions.