Transient/TrapDelete - error

I thought I’d start a new thread and leave the ChangeFSI discussion in peace.

“Internal error: abort on data transfer at &FC16770C (code 2613)”

The error repeats on each attempt to run Transient until you edit the choices file to not auto expire empty directories regardless of age.
Alternately add a file to the oldest directory and the error does not occur (because there is no empty directory other than todays).

So far I haven’t seen any aborts when expiring empty dirs. The line number (2613) doesn’t provide a clue either as it’s in a part that has nothing to do with auto-expiry.

How are the other expiry options set? Is this with any empty directory or only directories that used to have deleted objects in them (in which case the restore info might cause this)?

How are the other expiry options set? Is this with any empty directory or only directories that used to have deleted objects in them (in which case the restore info might cause this)?

Until I started unsetting options and testing variants all options were at default.

However, since you mention it, the directory had an item in it which I shift deleted a few days ago. The first boot since expire would have been valid. Does the shift-delete option not clear up relevant restore records?

Until I started unsetting options and testing variants all options were at default.

Thanks, I’ll experiment some more with default settings.

Does the shift-delete option not clear up relevant restore records?

No, TrapDelete doesn’t set up a job on Shift-Delete it just passes the messages straight on to FilerAction. Transient isn’t informed in any way so cannot update its restore info, the same thing would happen when objects are deleted from the TempDir when Transient isn’t running.

To keep the restore info up-to-date it may be necessary to periodically check that the objects being referred to still exist, say after each expiry. If there are many objects that may have to be done over several null events but that’s manageable.