Space rename on S3: a folder copy longer than 15 minutes never converges; a half copy at an abandoned target is never cleaned up or reported #969

Closed
opened 2026-10-19 00:20:30 +00:00 by Cordy · 0 comments
Owner

Found in the batch 3 reviews (review-c2, 2026-10-19). Pre-existing limits, made visible by #931.

  1. A long copy never finishes. On S3, convergence copies a renamed space's folder under a 15-minute bound. A resume copies every key again. So a folder that takes longer than 15 minutes to copy never converges:

    • every boot and every Retry now copies all of it again;
    • devices limited to folders in it wait in Moving each time;
    • the old name can never be retired.

    Expected: the copy makes progress across attempts (skip keys already copied and identical) or runs without a fixed bound, with progress visible on the admin row.

  2. Half copies are left behind. When a move target is abandoned (a second rename before the first converged, or copies-left), the partial copy at the old target stays. Nothing removes it and nothing reports it. It is claimed by the alias, so it is harmless, but it costs storage and confuses admins. Expected: it is listed on the space's admin row, and a clean-up action exists once nothing claims it.

Found in the batch 3 reviews (review-c2, 2026-10-19). Pre-existing limits, made visible by #931. 1. **A long copy never finishes.** On S3, convergence copies a renamed space's folder under a 15-minute bound. A resume copies every key again. So a folder that takes longer than 15 minutes to copy never converges: - every boot and every Retry now copies all of it again; - devices limited to folders in it wait in Moving each time; - the old name can never be retired. Expected: the copy makes progress across attempts (skip keys already copied and identical) or runs without a fixed bound, with progress visible on the admin row. 2. **Half copies are left behind.** When a move target is abandoned (a second rename before the first converged, or `copies-left`), the partial copy at the old target stays. Nothing removes it and nothing reports it. It is claimed by the alias, so it is harmless, but it costs storage and confuses admins. Expected: it is listed on the space's admin row, and a clean-up action exists once nothing claims it.
Cordy closed this issue 2026-10-27 12:22:54 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#969
No description provided.