Files on Tape but EOS Shows ARCHIVE_FAILED and d1::t0

Hi Team,
We are experiencing an issue with some files showing Redundancy: d1::t0.
We attempted to resubmit them with closew, but the operation failed. When checking the files with eos attr ls, they show an archive_id and an exception error.
Using cta-admin, we confirmed that the same files are present on tape, with the correct checksum and size.
On the EOS side, the logs report:
default SYNC::ARCHIVE_FAILED /eos/****80

In the CTA logs, we see messages indicating that the file was successfully written to tape:

“message”: “File successfully transmitted to drive”,
“drive_name”: “obelix_",
“instance”: “”,
“sched_backend”: “”,
“thread”: “TapeWrite”,
“tapeDrive”: “obelix_”,
“tapeVid”: "**”

However, the process then fails with the following error:
In ArchiveMount::reportJobsBatchTransferred(): got an exception
We attempted to clear the error and resubmit with closew again, but the same exception occurred. The EOS log once more shows:
default SYNC::ARCHIVE_FAILED /eos/***/******80
What is the recommended way to resolve this so that EOS displays the correct redundancy value?
Thank you

Hi Atefeh,

I just noticed that noone followed up on your issue. Were you able to resolve it or do you still need help?

Michael

Hi Mdavis,

Thanks you, this issue has been fixed.

1 Like