Mboxutil -R Process Runs For Hours Performing stat() (Doc ID 2735193.1)

Last updated on DECEMBER 08, 2020

Applies to:

Symptoms

An `mboxutil -R user/<USER>/INBOX` was started nearly 7 hours ago.

A truss was performed on the mboxutil process which ran for 8.34 seconds.
It produced 78,013 lines of doing stat() on *.msg files; that is about 9,350 per second.
The truss ran for almost 7 hours.
That would be 235,000,000 stat() calls.
There are only 220,000 *.msg files in the folder.
So it has done each of them an average of 1,000 times thus far.

Also to note, the truss slows it down.
So, for the vast majority of the nearly 7 hours, it has probably been doing A LOT more than 9k per second.

Yes, it would been better to have used `mboxutil -R -m user/<USER>/ user/<USER>/INBOX`instead.
But, it was assumed that the fix for internal Bug "Enh 27334204 - Optimize Mboxutil -R Restore Time By Caching Inodes" was supposed to improve this.

$ ps -ef|grep mbox

Those 29 lines are a single .msg file being restored.

Changes

Cause