Bug 7246 - max-size not working in 3.0.7 built from source with default configure
Summary: max-size not working in 3.0.7 built from source with default configure
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.0.7
Hardware: x86 Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
Depends on:
Reported: 2010-03-13 06:52 UTC by follow
Modified: 2011-02-22 09:22 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description follow 2010-03-13 06:52:46 UTC
If the max-size feature is a compile option, it's not mentioned in ./configure --help as such. If it's just supposed to be there, well, the option is accepted on the command line, but it's not effective. Invoking rsync with "--max-size=1m" on a directory with a 16g file in it and nothing else, it hangs there on the 16g file - probably transferring it, but it should have just said "No, this is too big," and finished, right?

So either the bug is that max-size needs to be documented in all the obvious places as an optional feature not in the default configuration (if that's the case), or it looks not to be working in 3.0.7.
Comment 1 Matt McCutchen 2010-03-17 02:29:52 UTC
--max-size works just fine for me:

$ rsync --version
rsync  version 3.0.7  protocol version 30
$ mkdir src dest
$ truncate -s 16G src/gigantic
$ rsync -vv --max-size=1m src/gigantic dest/
delta-transmission disabled for local transfer or --whole-file
gigantic is over max-size
total: matches=0  hash_hits=0  false_alarms=0 data=0

sent 31 bytes  received 12 bytes  86.00 bytes/sec
total size is 17179869184  speedup is 399531841.49

Are you doing something different?
Comment 2 Wayne Davison 2011-02-22 09:22:05 UTC
If there are more details, feel free to add them.  But this seems to be working fine.