fakeFPCheck reports corruption while reclaiming deduplication space
I am reclaiming deduplication storage space manually on a 5200 appliance. I am following the process in TECH180659.
I see a lot of these type of messages:
January 21 08:58:24 INFO : fakeFPCheck: DO 53c8979cafabfcc54c82cf7900fa465a is corrupt
January 21 08:58:26 INFO : fakeFPCheck: DO 546d2e925f2a6325c52884556187e102 is corrupt
And running the garbage collector doesn't seem to clean them up as they show up again the next passof running CR queue processing ( /usr/openv/pdde/pdcr/bin/crcontrol --processqueue).
Is there some way to clean up these corrupt fragments and reclaim the storage space?