Chris Lu a549580e65 ec.balance: verify shard landed on destination before deleting the source (#9858) ...

* ec.balance: verify shard(s) landed on the destination before deleting source

The EC balance task copied/mounted a shard to the destination and then
immediately unmounted+deleted it from the source, reporting success as soon
as the RPCs returned. A copy/mount can return OK while the shard isn't
actually registered/loadable on the destination, so deleting the source
then loses the shard (and the scanner re-issues the same move every cycle).

Add a verification step (VolumeEcShardsInfo via VerifyShardsAcrossServers,
the same check the EC encode task uses before deleting originals): if the
destination doesn't report every moved shard, fail the task and keep the
source so the move is retried instead of losing data.

* address review: use comma-ok when reading destination shard inventory

2026-06-07 21:31:53 -07:00

..

tasks

ec.balance: verify shard landed on destination before deleting the source (#9858)

2026-06-07 21:31:53 -07:00

types

Treat co-located volume servers as one fault domain when balancing and allocating (#9854)

2026-06-07 14:14:45 -07:00

client.go

fix(mini): shut down admin/s3/webdav/filer before volume/master on Ctrl+C (#9112)

2026-04-16 16:11:01 -07:00

log_adapter.go

Admin UI: Fetch task logs (#7114)

2025-08-09 21:47:29 -07:00

registry.go

chore: remove ~50k lines of unreachable dead code (#8913)

2026-04-03 16:04:27 -07:00

worker.go

fix(mini): shut down admin/s3/webdav/filer before volume/master on Ctrl+C (#9112)

2026-04-16 16:11:01 -07:00