ps. I am not sure whether this should be reported here or in the main irods repository.
What did you try to do?
I terminated the task that transfers an object from outside to iRODS
I terminated the task that transfers an object between two collections (copy ) in iRODS
Expected behavior
I expect interrupted transfers with errors in iRODS logs and also I expected objects exist in X/stale status
Observed behavior (including steps to reproduce, if applicable)
Transfers are terminated successfully and data objects have & status in irods and no error in the logs of iRODS
In line with other clients behavior, if a transfer to iRODS via globus is interrupted, the object status should be 'stale' instead of 'good'. This gets confused since data is partially written on destination not completely yet.
Logs in irods when a transfer via iCommands (or prc) is interupted:
Interrupted transfers should leave target replicas stale both either:
1) on successful client interruption (ctrl-c) and teardown OR
2) if the server has to clean up after an unclean client disconnect.
Bug Report
iRODS Version, OS and Version
4.3.0 almalinux8
ps. I am not sure whether this should be reported here or in the main irods repository.
What did you try to do?
Expected behavior
I expect interrupted transfers with errors in iRODS logs and also I expected objects exist in
X/stale
statusObserved behavior (including steps to reproduce, if applicable)
Transfers are terminated successfully and data objects have
&
status in irods and no error in the logs of iRODSIn line with other clients behavior, if a transfer to iRODS via globus is interrupted, the object status should be 'stale' instead of 'good'. This gets confused since data is partially written on destination not completely yet.
Logs in irods when a transfer via iCommands (or prc) is interupted: