From 7bfc9ca648dde8af4f20ffebcb124024e4870d95 Mon Sep 17 00:00:00 2001 From: ferrumclaudepilgrim Date: Tue, 11 Aug 2026 22:15:41 -0500 Subject: [PATCH] local: clarify what --local-fatal-if-no-space catches The flag applies to out of space errors while writing and while creating files or directories, not only while writing. Describe those operations without naming ENOSPC, which is a Unix error that Windows never reports, so the help is accurate on every platform. --- backend/local/local.go | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/backend/local/local.go b/backend/local/local.go index a8199f67e..91712f80d 100644 --- a/backend/local/local.go +++ b/backend/local/local.go @@ -311,10 +311,10 @@ set this flag.`, Name: "fatal_if_no_space", Help: `Make out-of-space errors fatal during transfers. -When enabled, an ENOSPC error during a write returns a fatal error so -that rclone aborts rather than retrying the operation. Useful for -backup scripts that should halt loudly on a full disk rather than spin -retrying.`, +When enabled, an out of space error while writing, creating a directory, +or creating a file returns a fatal error so that rclone aborts rather +than retrying the operation. Useful for backup scripts that should halt +loudly on a full disk rather than spin retrying.`, Default: false, Advanced: true, },