For a File based blobstore, temporary blobstore files are created under ./content/tmp directory.
The Admin - Remove a member from a blob store group task is intended to move all source blobstore *.bytes and *.properties files to another Group blobstore member, and then delete the source blobstore, if it is empty.
While the task makes the source blobstore read-only during this move, it also tries to move files that are temporary. When it does this, there could be errors loading these temporary files which fail the task. It also has been shown it is possible a blobstore can contain "temp" files that do not start with the expected "tmp$" prefix as the current task expects.
Do not move any temporary files from the source blobstore ( ie. ./content/tmp/** ) to a target group blobstore as NXRM cannot reliably read temporary files or resume using them in a different blobstore. Do not assume all "temp" files start with the prefix "tmp$" either - at least in older versions of NXRM3, having different named "temp" files seems possible.
Do not move files where a .properties file exists, but a bytes file does not and do not move files where a .bytes file exists, but a .properties file does not - instead log this condition with the found file name, the missing (expected) file name, and if one of the orphaned files is a properties file, log the contents of the properties file, without trying to parse it, in case the contents are corrupt or empty. Also log the file system create date of the found file. If these orphaned files are found, the task should continue and move all the valid blobstore files it can find.
S3 blobstores also have a temporary blob concept as well. Code review needs to be performed to see if S3 temp blobs are impacted in a similar way.