No, he got it right this time. It'a a recovery path, therefore there is no room for kXR_delete there. If you keep kXR_delete every write recovery will truncate the target file and continue pushing the chunks that it did not push so far resulting in a corrupted target.

In general, the timeout and recovery are the most complex parts of the client. I would refrain from fiddling with them unless you are sure you understood all the side effects for all the possible plugins including third-party, and then double and triple check. It took months to get right.

There is enough environment knobs to solve most problems, ie. you can disable the recovery altogether and let the tape server logic handle this aspect, if that is what you wish or just adjust the thresholds for when the connections are considered broken.

—
Reply to this email directly or view it on GitHub.

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1