Deduplication unoptimization issue

A

Aleksei Bondarenko

I'm trying unoptimize volume in my failover stretch cluster.

When i'm starting it, situation looked like this.

1293319.png

I expected that 4.5TB would be released and job finish. But after few days the disk space continued to run out and remained 5TB. I'm stoping unoptimize dedup job and run update-dedupstatus and get

1293323.png

why the saved space was 4.5TB, but the unoptimization task continues to work and the data has increased by more than 10TB?

Continue reading...
 
Back
Top Bottom