Bug 11111 - Describe the interaction between --one-file-system and --delete-excluded
Describe the interaction between --one-file-system and --delete-excluded
Status: NEW
Product: rsync
Classification: Unclassified
Component: core
All All
: P5 enhancement
: ---
Assigned To: Wayne Davison
Rsync QA Contact
Depends on:
  Show dependency treegraph
Reported: 2015-02-20 20:45 UTC by Bill McGonigle
Modified: 2015-02-20 20:50 UTC (History)
0 users

See Also:

rsync.yo patch (1.09 KB, patch)
2015-02-20 20:45 UTC, Bill McGonigle
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bill McGonigle 2015-02-20 20:45:11 UTC
Created attachment 10762 [details]
rsync.yo patch


  rsync --one-file-system --delete-excluded --exclude=/bar/ host:/bar/ /foo

where /bar is a mounted filesystem, 

document that ignoring a sender's "other" filesystem does not affect the operation of --delete-excluded at the matching receiver's patch (/foo/bar).

I ran into this under a pile of scripts where the backups first backed up /foo, then /foo/bar, then /foo/baz, and the underlying volume's CoW snapshots were quickly gaining size because /foo was listed in the excludes (first deleted, then re-populated).

The current documentation isn't wrong - just being explicit would help eliminate this as a gotcha.
Comment 1 Bill McGonigle 2015-02-20 20:50:43 UTC
argh - messed up the reduced example.  Should be host:/

  rsync --one-file-system --delete-excluded --exclude=/bar/ host:/ /foo