Re: [Bug 5478] rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)

On 17/04/18 17:47, just subscribed for rsync-qa from bugzilla via rsync wrote: > https://bugzilla.samba.org/show_bug.cgi?id=5478 > > --- Comment #34 from David Nelson --- > FYI. Although when rsync ver. 3.0.9 is called in Ubuntu 12.04LTS to "push" > files to the server, e.g.,

Re: Unfortunate results from fake-super

On 03/02/18 13:20, Dave Gordon via rsync wrote: > When using fake-super mode in an rsync receiver, anything that's neither a > file nor a directory (e.g. devices, symlinks, etc) is converted into a file, > and properties such as original ownership, filetype, and permissions are

Re: Unfortunate results from fake-super

On 03/02/18 15:52, Dave Gordon via rsync wrote: > On 03/02/18 13:20, Dave Gordon via rsync wrote: >> When using fake-super mode in an rsync receiver, anything that's neither a >> file nor a directory (e.g. devices, symlinks, etc) is converted into a file, >> and proper

Unfortunate results from fake-super

When using fake-super mode in an rsync receiver, anything that's neither a file nor a directory (e.g. devices, symlinks, etc) is converted into a file, and properties such as original ownership, filetype, and permissions are stored in a specific extended attribute. In the case of a symlink, the

Re: Unfortunate results from fake-super

On 05/02/18 23:03, Dave Gordon via rsync wrote: > On 05/02/18 05:53, Wayne Davison wrote: >> On Sat, Feb 3, 2018 at 5:20 AM, Dave Gordon via rsync >> <rsync@lists.samba.org <mailto:rsync@lists.samba.org>> wrote: >> >> [...fake-super symlink sav

Re: Unfortunate results from fake-super

On 05/02/18 05:53, Wayne Davison wrote: > On Sat, Feb 3, 2018 at 5:20 AM, Dave Gordon via rsync > <rsync@lists.samba.org <mailto:rsync@lists.samba.org>> wrote: > > [...fake-super symlink saved as a file...] > > This results in the copy being world-w

Re: Unfortunate results from fake-super

On 06/02/18 19:03, Dave Gordon via rsync wrote: [:snip:] > > The other part of this problem is that it doesn't at present seem > possible to satisfy all of three individually reasonable requirements of > a backup system at the same time: > > 1.The backup receiver (da

Re: rsync to my external eSATA HD is crashing/freezing my system...

On 25/03/18 15:32, Morgan Read via rsync wrote: > On 19/03/18 14:01, Morgan Read wrote: >> Hello list >> >> I've been running the following command, first in fc20 and then now >> (since the beginning of March) in fc26: >> now=$(date +"%Y%m%d-%H%M"); sudo rsync -ahuAESX -vi /home/ >>

Re: rsync time machine backup permissions

On 20/03/18 05:44, Andre Althoff via rsync wrote: > That doesn’t work too. :-( > > Last login: Mon Mar 19 19:18:16 on console > iMac:~ andre$ mount > /dev/disk0s2 on / (hfs, local, journaled) > devfs on /dev (devfs, local, nobrowse) > map -hosts on /net (autofs, nosuid, automounted, nobrowse) >

Re: [Bug 13364] rsyncd clips trims relative symlinks outside of source tree

On 04/04/18 20:52, just subscribed for rsync-qa from bugzilla via rsync wrote: > https://bugzilla.samba.org/show_bug.cgi?id=13364 > > --- Comment #3 from Chris Severance --- >> enable munge-symlinks. That way the client will get back the same >> out-of-tree

Re: rsync time machine backup permissions

On 03/04/18 18:08, Michael wrote: > On 2018-04-03, at 4:05 AM, Dave Gordon via rsync <rsync@lists.samba.org> > wrote: > >> On 20/03/18 05:44, Andre Althoff via rsync wrote: >>> That doesn’t work too. :-( >>> >>> Last login: Mon Mar 19 19:18:16 on

Re: rsync time machine backup permissions

On 20/03/18 05:51, Michael via rsync wrote: > What is the order that rsync uses to set permissions? > > Time Machine directories have ACL permissions that basically prohibit making > any changes of any kind. In order to make a backup of the directory, you > would need to set those permissions

Re: file contents cause rsync to fail (with certains args and dir structure)

Quite strange at first sight that the failure should depend on the files containing NULs! But I've reproduced it on both Ubuntu and OpenSUSE with d73762e "Preparing for release of 3.1.3". The problem remains even if you drop the --checksum or --delay-updates options from the command line, but

Re: file contents cause rsync to fail (with certains args and dir structure)

in the destination file using newer Linux fallocate features. It also supports a --whole-file + --sparse + --inplace copy on any filesystem by truncating the destination file. .Dave. Sent using Zoho Mail On Sun, 04 Mar 2018 23:17:23 +0100 Dave Gordon via rsync rsync@lists.samba.org wrote

Re: Kudos and feature question

I think you would implement it as a new type of filter rule. similar to 'P' (preserve) but with a timestamp or delta-time to define what counts as 'recent' as well as the pattern to match for this rule to apply (which could just be a wildcard matching anything by default, but could also use the

Re: rsync many processes and slow backup

>>> Hi all! :-) >>> >>> I have a small rsync script to sync my data to a usb-disk. It works >>> fine, when I start it in console. I get 3 rsync processes (look in >>> top) and the backup takes ~25 min. But, when I add the script in >>> cron to start it at 1am at night it takes 7 - 9 hours and I

Re: [Bug 12769] error allocating core memory buffers (code 22) depending on source file system

On 11/10/2019 13:53, just subscribed for rsync-qa from bugzilla via rsync wrote: > https://bugzilla.samba.org/show_bug.cgi?id=12769 > > --- Comment #5 from Simon Matter --- > I'm suffering the same problem and was wondering if anyone found a solution or > work around or other tool to do the job?

Re: rsync error

On 25/06/2020 13:18, Madhurananda Pahar via rsync wrote: > Hello everybody,  > >          I am having a funny problem while using rsync as a tool to > back-up my files:  > > [sender] expand file_list pointer array to 524288 bytes, did move. > > I am just wondering if you had this issue before