we're deduping a 2.5TB fs and it's been busy for a couple of days.
Since yesterday, it looks like it's stuck at 95%, Scanning status is not being updated anymore.
server_df of of this FS is still showing a decrease in space used and as it's the only process makeing use of this FS, it can only be the dedupe process compressing/dedupping the data. When we also check the server_stats, we're also seeing an average of around 6MB/s read and write to this FS.
Anyone any idea why it's not updating the Scanning status.
The F-RDE Policy Engine does not actually know how many real files (vs directories, links, etc) are on the filesystem when it starts the scan so it estimates the value based on the number of used inodes. Since this value may be somewhat inaccurate and we do not want to exceed 100% complete or hit 100% too early, it stops at 95% until the scan is complete.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
451
0
Posted May 5th, 2011 06:00
what if you suspend dedupe and then resume it ?