From dfce24b9eb5c5e1f8bfeb380553097f3b718de76 Mon Sep 17 00:00:00 2001 From: Parshant Sharma Date: Wed, 21 Jan 2026 15:02:22 +0530 Subject: [PATCH] docs(volumes): note machine replacement when removing mounts --- volumes/volume-manage.html.markerb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/volumes/volume-manage.html.markerb b/volumes/volume-manage.html.markerb index 43396d95b8..b7e8506cb8 100644 --- a/volumes/volume-manage.html.markerb +++ b/volumes/volume-manage.html.markerb @@ -203,7 +203,7 @@ Volumes attached to Machines can’t be destroyed. You can check which Machine ( If you’re replacing the Machine, use `fly scale count` or `fly machine clone` to launch a new one. This will create and mount a fresh volume based on your `fly.toml` config. -To stop using volumes entirely, remove any `[mounts]` from `fly.toml`, redeploy to detach them, and then destroy the volumes. +To stop using volumes entirely, remove any `[mounts]` from `fly.toml` and redeploy. The Machine will be replaced without the volumes. After redeploying, you can destroy the volumes. **Note:** Snapshots taken before deletion may still be restorable for a limited time, provided you have the volume ID (default retention is 5 days).