v0.303.0 (code): after a restart, a backup capture waits for the drive's bind (R-897)
gates / gates (push) Successful in 1m18s
gates / gates (push) Successful in 1m18s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -450,6 +450,11 @@ func (m *Manager) captureAllRecoveryUnits(dataRun bool) {
|
||||
if m.settings != nil && (m.settings.IsDisconnected(drivePath) || m.settings.IsDecommissioned(drivePath)) {
|
||||
continue // drive not writable — skip, the existing unit stays as-is
|
||||
}
|
||||
// R-897: right after a boot the agent may still be (re)binding the drive; a capture in that second failed
|
||||
// with "permission denied" (measured on demo-hp 2026-10-07). Wait for the bind — bounded (driveready.go).
|
||||
if !m.driveReady(drivePath, dataRun) {
|
||||
continue
|
||||
}
|
||||
// Slice 4: a HELD app's unit is its RESTORE POINT, and the hold text names that copy's date.
|
||||
// Re-capturing it would write the definition the app is held ON (after a failed update: the new
|
||||
// version that would not start) into the unit, and the next Tier-2 run would mirror it over the
|
||||
|
||||
Reference in New Issue
Block a user