When running PMOF jobs with large volumes of data, it is common that FSDAX files cannot be deleted,thus affecting the next Job running.
For example, when running a 2TB Terasort test, the FSDAX file cannot always be deleted.
The potential problem might be in cleaning up the pool, but FSDAX does not need to clean up the pool and can directly delete files using POSIX operations.
Therefore, it is recommended to separate the fsdax file deletion operation from devdax.
When running PMOF jobs with large volumes of data, it is common that FSDAX files cannot be deleted,thus affecting the next Job running. For example, when running a 2TB Terasort test, the FSDAX file cannot always be deleted. The potential problem might be in cleaning up the pool, but FSDAX does not need to clean up the pool and can directly delete files using POSIX operations. Therefore, it is recommended to separate the fsdax file deletion operation from devdax.