NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled. We're excited to launch our new Community experience on July 30 and more information will follow soon. Stay connected during the transition - Join our Discord community today.
The AltaVault device (running 4.4) in the production environment of mine has been running garbage collection for about 24 hours now. It is stuck at 0%.
rfsctl exec gc command shows that the gc.cadidate_slabs is incrementing.
How long will this job run ? Is there a way to identify the % complete?
I have seen cases where the AltaVault garbage collection (GC) may get hung up in this pending state due to issues with consistent cloud connectivity. For example, before data is deleted (say, by eviction), AltaVault checks that data is safely in cloud storage and is current. These checks could timeout, which would add latency to the eviction and GC processing. Is there eviction ongoing with this workload, or is the GC running checks? Have you previously seen GC run longer? Have there been any connectivity issues with the cloud provider (i.e. pings take longer, or packets lost/timeout)?
