Perhaps a workaround is to rig up a second JobHistoryServer looking at the new "large file" root, as long as we still maintain the same directory structure, it may be able to pick up the files there.
In that case we don't completely loose ability to have customers use the normal UI to analyise job more than a few minutes after finishing, but they would have to skip to a different location.