[Bug 14962] Crash/restart using rsync 3.2.3 on M1 Mac

2022-01-27 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=14962

--- Comment #1 from Mike Bombich  ---
This is probably the same kernel memory leak I documented here:

https://bombich.com/kb/ccc6/macos-monterey-known-issues#smb_panics

You can confirm whether it's the same issue by looking for zone_map_exhaustion
in the system log. e.g.:

- Start your rsync task
- Run `log --stream | grep zone_map_exhaustion` in a Terminal window
- Run `sudo zprint -d kext.kalloc.32768` in another Terminal window

Also watch memory pressure in Activity Monitor. I saw a gradual and steady
increase, although it never got to a "warning" level before memoryd started
killing things.

If that's what you're seeing, it's not an rsync bug, it's a bug in macOS.

Mike

> On Jan 27, 2022, at 11:26AM, just subscribed for rsync-qa from bugzilla via 
> rsync  wrote:
> 
> https://bugzilla.samba.org/show_bug.cgi?id=14962
> 
>Bug ID: 14962
>   Summary: Crash/restart using rsync 3.2.3 on M1 Mac
>   Product: rsync
>   Version: 3.2.0
>  Hardware: All
>OS: All
>Status: NEW
>  Severity: normal
>  Priority: P5
> Component: core
>  Assignee: wa...@opencoder.net
>  Reporter: arjunm...@gmail.com
>QA Contact: rsync...@samba.org
>  Target Milestone: ---
> 
> Hi there,
> 
> Whole (macOS) system is crashing when transferring a large number of files 
> from
> Mac to NAS via rsync.
> 
> Running the below command on a directory with thousands of images (~5MB each)
> the transfer speed eventually slows down, the system gets choppy, freezes and
> then eventually the entire computer reboots.
> 
> rsync -va --update --info=progress2 /Volumes/Source/folder
> /Volumes/Destination/folder
> 
> I found this reported here as well:
> https://apple.stackexchange.com/questions/421007/rsync-3-2-3-keeps-crashing-on-mac-mini-m1#
> 
> I experienced this on a M1 Mac mini running macOS Monterey. The stackexchange
> post is running Big Sur.
> 
> rsync 3.2.3 was installed via homebrew (brew install rsync) so it may be
> possible this is a homebrew distribution/compile problem.
> 
> The only solution for me was to downgrade back to use the included rsync in
> macOS (rsync version 2.6.9 protocol version 29)
> 
> -- 
> You are receiving this mail because:
> You are the QA Contact for the bug.
> -- 
> Please use reply-all for most replies to avoid omitting the mailing list.
> To unsubscribe or change options: 
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: trailing spaces in exclude-from file

2022-01-27 Thread Wayne Davison via rsync
On Mon, Jan 24, 2022 at 1:08 AM Jürgen Bausa via rsync <
rsync@lists.samba.org> wrote:

> However, it didn't work in the beginning and took me some time to find
> out, that a space at the end (e.g. "+ /mnt/Windows/Users " in the second
> line) will be interpreted and thus, the directory is assumed to be "Users "
> and not "Users".


When working on some filter rules it helps to use --debug=FILTER or
--debug=FILTER2 options. (While these are implied by -vv and -vvv
respectively, it's better to be more specific in what you want to debug.)
The FILTER2 level mentions the add_rule(RULE_HERE) call where a trailing
space would be visible prior to the trailing paren, though it might not be
immediately obvious.  I've just made a change in git that makes rsync
output a warning message in either debug-filter level if there is a
trailing space or tab on a rule, which will help someone notice it if they
didn't intend to specify it.

..wayne..
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 14962] New: Crash/restart using rsync 3.2.3 on M1 Mac

2022-01-27 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=14962

Bug ID: 14962
   Summary: Crash/restart using rsync 3.2.3 on M1 Mac
   Product: rsync
   Version: 3.2.0
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P5
 Component: core
  Assignee: wa...@opencoder.net
  Reporter: arjunm...@gmail.com
QA Contact: rsync...@samba.org
  Target Milestone: ---

Hi there,

Whole (macOS) system is crashing when transferring a large number of files from
Mac to NAS via rsync.

Running the below command on a directory with thousands of images (~5MB each)
the transfer speed eventually slows down, the system gets choppy, freezes and
then eventually the entire computer reboots.

rsync -va --update --info=progress2 /Volumes/Source/folder
/Volumes/Destination/folder

I found this reported here as well:
https://apple.stackexchange.com/questions/421007/rsync-3-2-3-keeps-crashing-on-mac-mini-m1#

I experienced this on a M1 Mac mini running macOS Monterey. The stackexchange
post is running Big Sur.

rsync 3.2.3 was installed via homebrew (brew install rsync) so it may be
possible this is a homebrew distribution/compile problem.

The only solution for me was to downgrade back to use the included rsync in
macOS (rsync version 2.6.9 protocol version 29)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html