Release 2026.09.27.r002: clarify rsync dry runs and expand run diagnostics
This commit is contained in:
@@ -73,3 +73,20 @@ already be mounted, for example through Unassigned Devices. URBM checks array an
|
||||
USB mounts before starting the job and refuses leftover directories after an
|
||||
unmount. Keep the USB disk connected throughout the run. Reload the page after
|
||||
mounting a new array disk to refresh the available sources.
|
||||
|
||||
### Rsync diagnostics (2026.09.27.r002)
|
||||
|
||||
Run logs start collapsed and retain your open/closed selection during refresh.
|
||||
New Rsync runs log the source paths, target, dry-run mode, overwrite/delete and
|
||||
comparison options, exclusions, execution phases, up to 20 itemized change
|
||||
examples, and final file/byte/deletion totals. Deletion counts include directories
|
||||
and symlinks. Byte totals describe the contents of transferred files, not protocol
|
||||
traffic. A dry run reports planned changes and records zero bytes actually copied;
|
||||
its notification explicitly states that no changes were made. Historical logs
|
||||
cannot be reconstructed with these additional details.
|
||||
|
||||
For an integration test against Rsync 3.x, run
|
||||
`URBM_TEST_RSYNC=/path/to/rsync go test ./internal/rsync -run TestRealRsync -v`.
|
||||
The test uses temporary directories only and checks that a dry run changes nothing,
|
||||
that a subsequent copy matches the planned counts, and that another comparison
|
||||
then finds no changes.
|
||||
|
||||
Reference in New Issue
Block a user