A simple bpcp copy from local to remote leaves a cfdp.1.x file remnant in the ION directory of remote machine.
example: bpcp ./data/data1.dat 2:./data/data.dat
This is not a bpcp problem. It also happens with cfdptest. It looks like at the remote node, data is aggregated into temporary file: cfdp.x.y and then file is moved to final destination folder. temp file does not seem to be deleted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As of 4.1.4, the temporary file only remains if the filestore command did not complete. This happens when a file with the same name already exist in the destination folder. In that case the file is saved as cfdp.x.y where x is the source node number and y is the a monotonically increasing number. The pair x.y is the transaction id.
This is not an issue. We believe leaving the file in place, identifiable by the transaction ID is sensible for users who wants to retrieve the file if needed.
Closing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is not a bpcp problem. It also happens with cfdptest. It looks like at the remote node, data is aggregated into temporary file: cfdp.x.y and then file is moved to final destination folder. temp file does not seem to be deleted.
As of 4.1.4, the temporary file only remains if the filestore command did not complete. This happens when a file with the same name already exist in the destination folder. In that case the file is saved as cfdp.x.y where x is the source node number and y is the a monotonically increasing number. The pair x.y is the transaction id.
This is not an issue. We believe leaving the file in place, identifiable by the transaction ID is sensible for users who wants to retrieve the file if needed.
Closing.