* 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>
* test: live move keeps the source frozen across a reload, on Go and Rust volume servers
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: require 409 from the reloaded frozen source
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume_move: reopen an interrupted move's source only without a target copy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>