Chris LuandClaude Opus 5.5 49bb6bb8c4 volume_move: persist the move's source freeze across reloads ...

A live move froze the source in memory only, so an unmount/mount or a
volume server restart mid-move reopened it for writes that the move then
deletes with the source. Persist the freeze when the move froze a
writable source, and reopen the target right after the copy since the
copied .vif carries the freeze. An already-readonly source keeps an
in-memory mark, and a failed move still restores the source writable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-12 17:01:57 -08:00

..

ec_move_test.go

EC: handle zero-sized shard files uniformly (moves, rebuilds, startup cleanup) (#10753)

2026-08-13 21:38:22 -07:00

ec_move.go

ec: re-plan balance moves when a target reports no space left (#11759)

2026-10-15 18:47:07 -07:00

fake_client_test.go

volume_move: persist the move's source freeze across reloads

2026-11-12 17:01:57 -08:00

mover.go

refactor: share volume and EC shard move logic between shell and workers (#10727)

2026-08-12 12:29:40 -07:00

volume_move_test.go

volume_move: persist the move's source freeze across reloads

2026-11-12 17:01:57 -08:00

volume_move.go

volume_move: persist the move's source freeze across reloads

2026-11-12 17:01:57 -08:00