Unsolved
2 Posts
0
1072
June 3rd, 2020 00:00
full disk usage
Hello,
I have a problem with avamar 7.4
Via SSH we can see that my disks are almost full, but in Avamar GUI I see utilization below 50%.
And of course I have read only mode and gsan status: degraded
Ive tried to backup one very big server, after backup I removed it but as you can see below - my disk isn't cleaned up.
admin@avamar://>: df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 7.9G 4.5G 3.1G 60% /
udev 7.7G 256K 7.7G 1% /dev
tmpfs 7.7G 0 7.7G 0% /dev/shm
/dev/sda1 114M 31M 78M 28% /boot
/dev/sda3 895G 876G 19G 98% /data01
/dev/sda7 1.5G 144M 1.3G 11% /var
/dev/sdb1 930G 906G 25G 98% /data02
/dev/sdc1 930G 904G 27G 98% /data03
No Events found!
ionthegeek
2 Intern
•
2K Posts
0
June 3rd, 2020 05:00
This system is almost certainly failing its daily data integrity check (hfscheck). If a system is failing hfscheck, it will retain the last checkpoint that passed validation to ensure there is a known good point in time available for a rollback. Checkpoints are similar to snapshots, so as the checkpoint ages, checkpoint overhead will build up as differences between the validated checkpoint and the current data build up, leading to an increase in disk utilization.
Please contact support as soon as possible for assistance. Once the hfscheck issue is resolved and the system is able to validate a checkpoint, the old checkpoint will be rolled off and the disk space being consumed by checkpoint overhead will be freed. Hopefully this goes without saying but it is vitally important that the validated checkpoint not be removed. Deleting the validated checkpoint may lead to catastrophic system failure.
pszemo
2 Posts
0
June 4th, 2020 02:00
I rolled avamar to previous valid 'snapshot' but now MCS status is down, and when I running "mcserver.sh --start" then I have:
WARNING: Insufficient privilege to create accounts and perform backups.
ERROR: gsan rollbacktime: 1591180617 does not match stored rollbacktime: 1588347908
ionthegeek
2 Intern
•
2K Posts
0
June 4th, 2020 11:00
The error message shown appears when the MCS has not been rolled back following a rollback of the GSAN. Normally, the dpnctl utility is used to roll a system back to ensure that GSAN and MCS are rolled back at the same time. The MCS and GSAN need to be in sync at all times in order to avoid issues like client ID mismatches that can cause subtle problems that are difficult and time consuming to troubleshoot.
The warning message you posted also makes me concerned that there is still some underlying issue with the GSAN that has not been addressed.
I strongly recommend that you work with support on this.