Re: rsync whole file transfers extremely slow over SSH - but only in a particular virtual guest

On Wed 15 May 2024, Graham Leggett via rsync wrote: > > Then we check the disk underneath rsync: > > [root@arnie images]# dd if=/dev/urandom of=random.img count=1024 bs=10M > status=progress > 1604321280 bytes (1.6 GB, 1.5 GiB) copied, 16 s, 100 MB/s^C > 159+0 records in > 159+0 records out >

rsync whole file transfers extremely slow over SSH - but only in a particular virtual guest

Hi all, I am trying to get to the bottom of a strange rsync performance problem. On a specific guest OS, and only on this guest OS, rsync is giving modem-like transfer speeds. This happens on delta transfers, and whole file transfers. [root@arnie ~]# rsync -avz --progress --sparse

Re: rsync as a de-duplication-only tool, using --link-dest

I don't believe that what you are asking for can be done with rsync. At first thought you can't mix --ignore-existing with --ignore-non-existing as that would ignore everything. Something would have to at least exist and not be ignored for rsync to link to it. Anyway, for a laugh, I asked

rsync as a de-duplication-only tool, using --link-dest

Recently I was thinking about --link-dest= and if it was possible to use rsync to de-duplicate two nearly-identical directory structures. Normally I would use a tool like hardlink, jdupes, or rdfind, but in this case the files are huge and numerous, so hashing them would take forever. I did a

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 4592aa77 More tweaks for Actions. from 8bc363cc Separate the builds and make Cygwin always run. https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log - commit

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 8bc363cc Separate the builds and make Cygwin always run. via a9a31557 Work around pkg install issue. from fcc79836 Get fetch-depth:0 right. https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via fcc79836 Get fetch-depth:0 right. from 804411b7 Get rid of gensend target & cached git version. https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log - commit

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 804411b7 Get rid of gensend target & cached git version. via 0b1b2a3f Get the "dev" suffix right. via 50bdf968 Remove duplicate paragraph. via 3f2a38b0 CI: added Solaris build from 5510255f Tweak maintainer messaging.

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 5510255f Tweak maintainer messaging. via 56a039b0 Changes for 3.3.1dev. from 7bc3be2b CI: fixed rules for when to trigger https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 7bc3be2b CI: fixed rules for when to trigger via 411c4789 support: added install_deps_ubuntu.sh via 231b239f check for stpcpy via 4c8683c8 update to popt 1.19 via 85c906f9 Silence unused var warning via

RE: Rsync 3.3.0 released

Hi Wayne, Just an FYI: RSync 3.3.0 built for HPE NonStop x86 and ia64 is now available on the ITUGLIB website (my team). We have supported that community and platform for many years. I am unsure how best to notify the RSync team about this. Regards, Randall From: rsync On Behalf Of

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via ae3e13ba Update github links. from 6c8ca91c Preparing for release of 3.3.0 [buildall] https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log - commit

[rsync-announce] Rsync 3.3.0 released

I have released rsync version 3.3.0. This is a bug fix release, with the increased version bump being a delayed reaction to some of the recent larger changes that have happened. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.3.0 You can

Rsync 3.3.0 released

I have released rsync version 3.3.0. This is a bug fix release, with the increased version bump being a delayed reaction to some of the recent larger changes that have happened. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.3.0 You can

[SCM] The rsync repository. - annotated tag v3.3.0 created

The annotated tag, v3.3.0 has been created at df60f6aa84e3ba9f251dde205f3ed03726b37137 (tag) tagging 6c8ca91c731b7bf2b081694bda85b7dadc2b7aff (commit) replaces v3.3.0pre1 tagged by Wayne Davison on Sat Apr 6 09:38:26 2024 -0700 - Log

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 6c8ca91c Preparing for release of 3.3.0 [buildall] from 079e74a3 Some year updates. https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log - commit

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 079e74a3 Some year updates. via abc3c746 Mention latest changes in NEWS. via 99ab5946 exclude: fix crashes with fortified strlcpy() from a47ae6fa typo in rsyncd.conf.5.md https://git.samba.org/?p=rsync.git;a=shortlog;h=master

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via a47ae6fa typo in rsyncd.conf.5.md from 2f9b963a Make `--max-alloc=0` safer. https://git.samba.org/?p=rsync.git;a=shortlog;h=master - Log - commit

[SCM] The rsync repository. - branch master updated

The branch, master has been updated via 2f9b963a Make `--max-alloc=0` safer. via 3476caea Convert mnt-excl into python. via 6f3c5ecc Fix old stats bug that counted devices as symlinks. via 79fda353 A couple more NEWS improvements. from cd769934 Mention

ACLs vanish while transferring files

Hi all, I'm trying to transfer data from the old fileserver to the new cluster using rsync. Depending on how I define the source path either the folder acls are transfered or the file acls. This command preserves the file acls: # rsync -AavXz --numeric-ids --delete /winhome

[Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #41 from Mihnea-Costin Grigore --- The discussion about file systems like ZFS/BTRFS/etc. and their various snapshot mechanisms is off-topic relative to this feature request, since they are very different technologies used for different

Re: rsync segfaults when openssl fips is enabled

This happens with rsync-3.2.4, upgraded to v3.2.7 and this is solved. Thanks. -- Shedi On Tue, Mar 12, 2024 at 3:05 PM Shreenidhi Shedi < shreenidhi.sh...@broadcom.com> wrote: > Hi All, > > Any inputs on this issue? > > -- > Shedi > > > On Wed, Feb 21, 2024 at 5:12 PM Shreenidhi Shedi < >

[PATCH] add option to skip files based on age/mtime

I've added the options --min-age=SECONDS and --max-age=SECONDS to allow rsync to skip files based on how recently they were modified. Setting --min-age=30 (for example) would cause rsync to skip files that had been modified within the last 30 seconds. Setting --max-age=7776000 would cause

Re: rsync Digest, Vol 255, Issue 2

Shedi I suggest upgrading rsync to a modern hash. For example, Blake3. On Tue, Mar 12, 2024, 8:00 a.m. wrote: > Send rsync mailing list submissions to > rsync@lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit >

Re: rsync segfaults when openssl fips is enabled

Hi All, Any inputs on this issue? -- Shedi On Wed, Feb 21, 2024 at 5:12 PM Shreenidhi Shedi < shreenidhi.sh...@broadcom.com> wrote: > Hi All, > > Copying the content from the GH issue as is. > Need your inputs on the same. > FWIW, the coredump files generated in linux have xattr values which

[Bug 6741] 'deleting' messages show up in improper places

https://bugzilla.samba.org/show_bug.cgi?id=6741 --- Comment #5 from Marc Aurèle La France --- Created attachment 18263 --> https://bugzilla.samba.org/attachment.cgi?id=18263=edit rsync stdout filter Just something I've come up with to work around this issue. Not perfect but does the job.

rsync segfaults when openssl fips is enabled

Hi All, Copying the content from the GH issue as is. Need your inputs on the same. FWIW, the coredump files generated in linux have xattr values which are > 32 bytes. https://github.com/WayneD/rsync/issues/569 Hi All, System details: root@ph3dev [ ~ ]# rsync --version rsync version 3.2.4

[Bug 15585] New: rsync ends still with error 22 when try to deleting many files

https://bugzilla.samba.org/show_bug.cgi?id=15585 Bug ID: 15585 Summary: rsync ends still with error 22 when try to deleting many files Product: rsync Version: 3.2.0 Hardware: All OS: All Status:

tests for clone-dest

WayneD's clone-dest patch seems to be working for me, it's available here: https://github.com/WayneD/rsync-patches/blob/master/clone-dest.diff I've written some very basic tests, which I've attached to this email, in case they are of use to anyone else. They're also available here:

Re: rsync replacing symlinks without warning (resend)

I'm not really blaming the user. If it were up to me, -v would include -i. On 2/9/24 05:36, Andreas Gruenbacher wrote: On Sun, Feb 4, 2024 at 7:20 PM Kevin Korb via rsync wrote: rsync's -v is fairly useless. Learn to use -i instead or in addition to. Well, note that I didn't say anything

Re: rsync replacing symlinks without warning (resend)

On Sun, Feb 4, 2024 at 7:20 PM Kevin Korb via rsync wrote: > rsync's -v is fairly useless. Learn to use -i instead or in addition to. Well, note that I didn't say anything about the lib/ directory in that command; it's just that rsync decided to remove the symlink component from the path

[Bug 2294] Detect renamed files and handle by renaming instead of delete/re-send

https://bugzilla.samba.org/show_bug.cgi?id=2294 --- Comment #39 from andy --- > This feature request is so old it has lost relavence because btrfs/zfs/etc > are more optimal backup solutions than rsync. Funny I am doing exactly this, but I came to rsync looking for a backup for when ZFS fails.

Re: BUG? rsync ends without message by delete files

now it sounds like you have too many hard links for rsync to handle. On 2/7/24 08:05, Franke via rsync wrote: Am 06.02.24 um 23:20 schrieb Roland: and then, it stops totally quiet. you mean it simply exits without any message? Yes rsync ends totally quit. what's the return code ( echo

Re: BUG? rsync ends without message by delete files

here is another report of this behaviour. https://unix.stackexchange.com/questions/754923/rsync-just-stops nothing appropriate in bugzilla, besides https://bugzilla.samba.org/show_bug.cgi?id=13317 do you use zfs or is there full-space/quota condition while running? if you can't resolve, please

Re: BUG? rsync ends without message by delete files

and then, it stops totally quiet. you mean it simply exits without any message? what's the return code ( echo $? ) roland Am 06.02.24 um 22:18 schrieb Franke via rsync: Hi Kevin, Am 06.02.24 um 20:55 schrieb Kevin Korb: The other likely cause is your $SOURCE being something that contains

Re: BUG? rsync ends without message by delete files

Normally, when rsync isn't deleting things the problem is that there is some kind of error (possibly scrolled off screen unnoticed) but it sounds like you are getting no output at all which would eliminate that possibility. The other likely cause is your $SOURCE being something that contains a *

Re: rsync replacing symlinks without warning (resend)

rsync's -v is fairly useless. Learn to use -i instead or in addition to. On 2/4/24 12:58, Andreas Gruenbacher via rsync wrote: Hello, when trying to rsync files between hosts, I ran into a surprising case in which rsync replaces a symlink with a directory, with no indication of any kind. In

rsync replacing symlinks without warning (resend)

Hello, when trying to rsync files between hosts, I ran into a surprising case in which rsync replaces a symlink with a directory, with no indication of any kind. In the following reproducer, rsync is called as follows: rsync --verbose --recursive --relative --delete a/./lib/modules b/

Release the fix for the argv use-after-free issue with popt 1.19?

I'm using Fedora 38's rsync-3.2.7-2.fc38.x86_64 package, and the other day, I noticed that one of my backup scripts was creating directories with garbage names. Eventually I tracked the problem down to the argv use-after-free issue with popt 1.19 that was fixed in commit

Re: Archiving to vfat

--modify-window was it, thanks very much. Works flawlessly now. Thanks also for the s,a,rt, tip. -- Ian -- 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:

Re: Archiving to vfat

Also, instead of -a use -rt. Those are the only parts of -a that FAT even pretends to support. On 1/21/24 16:42, Roland via rsync wrote: it's most likely because of vfat timestamp limitation try --modify-window   When comparing two timestamps, rsync treats the timestamps as

Re: Archiving to vfat

it's most likely because of vfat timestamp limitation try --modify-window   When comparing two timestamps, rsync treats the timestamps as being equal if they differ by no more than  the modify-window   value.   This  is  normally  0 (for an exact match), but you may find

Archiving to vfat

I am trying to use rsync between two local directories on Linux. The source directory is on a normal ext4 partition, under my home directory. The destination is an SD card that I insert into the card reader on the computer, formatted with a vfat filesystem. The command line is like rsync -avC

Re: Everything working as expected, so shouldn't ERROR be WARNING

On Thu, 18 Jan 2024, Paul Slootman via rsync wrote: On Thu 18 Jan 2024, Roger Price via rsync wrote: I get the messages sending incremental file list ERROR: daemon refused to receive file "rprice/demo.dvi" I understand that the remote daemon has refused file demo.dvi because I specifically

Re: Everything working as expected, so shouldn't ERROR be WARNING

On Thu 18 Jan 2024, Roger Price via rsync wrote: > I am backing up a user's directories from local machine titan to remote > machine maria. On the remote machine maria file /etc/rsyncd.conf contains > > [rprice-home] > ... > exclude = *.dvi > > I start the backup by using this command on the

Everything working as expected, so shouldn't ERROR be WARNING

I am backing up a user's directories from local machine titan to remote machine maria. On the remote machine maria file /etc/rsyncd.conf contains [rprice-home] ... exclude = *.dvi I start the backup by using this command on the local machine titan: rprice@titan ~ rsync -av --dry-run

[PATCH] Fix INET6 detection on recent clang

The implicit int return for main() in the configure test for INET6 is now a hard error on recent clang, breaking the detection of IPv6 support. Update this to int main(void) like the other configure tests. The problem this causes in practice is quite subtle and easy to miss. ssh is always run

Re: process --files-from filelist as given

Hi. On Sun, 31 Dec 2023 20:28:21 +0100 Roland via rsync wrote: > apparently, rsync sorts the list of files  provided to "--files-from". > how can i avoid sorting of that list ? According to the man, this is not possible. See: SORTED TRANSFER ORDER that suggest also the --delay‐updates option.

[Bug 15546] New: disable of sorting when files to transfer is fed via --files-from

https://bugzilla.samba.org/show_bug.cgi?id=15546 Bug ID: 15546 Summary: disable of sorting when files to transfer is fed via --files-from Product: rsync Version: 3.2.0 Hardware: All OS: All

Re: process --files-from filelist as given

I want to copy a list of files in specific order Why ? because i want to serialize files on disk so they are stored on disk in the order being accessed regularly i built that list for --files-from   via output from fatrace tool. i now did use tar to transfer the files i will add an RFE to

process --files-from filelist as given

hello, apparently,  rsync sorts the list of files  provided to "--files-from". how can i avoid sorting of that list ? I want to copy a list of files in specific order regards Roland -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change

Re: rsync over ssh fails with --files-from

> The errors column is 0. The drop column is 18. The second bit number > is the number of packets which should grow. At least that is how I read > it. Column makes it more readable in a terminal but not so much in an > email. > Yes, my apologies. I even debated inserting a screenshot. errs

Re: rsync over ssh fails with --files-from

The errors column is 0. The drop column is 18. The second bit number is the number of packets which should grow. At least that is how I read it. Column makes it more readable in a terminal but not so much in an email. On 12/21/23 14:18, Alex wrote: Can someone help me determine if these

Re: rsync over ssh fails with --files-from

Can someone help me determine if these errors are normal or if this could somehow be the cause? I've removed the last three columns for readability - they were all zeros. # column -t /proc/net/dev Inter-| Receive|Transmit face |bytes packets errs drop fifo

Re: rsync over ssh fails with --files-from

Hi, On Wed, Dec 20, 2023 at 11:03 AM Kevin Korb via rsync wrote: > What is the error? I assume you know that with that syntax the > filelist.txt is local rather than remote. > Yes, I do know it refers to the list of local files. There is no error - it just hangs indefinitely until some

Re: rsync over ssh fails with --files-from

What is the error? I assume you know that with that syntax the filelist.txt is local rather than remote. On 12/20/23 09:50, Alex via rsync wrote: Hi, I've been using rsync on fedora over ssh to sync directories for decades, but suddenly having a problem with transferring multiple files at a

rsync over ssh fails with --files-from

Hi, I've been using rsync on fedora over ssh to sync directories for decades, but suddenly having a problem with transferring multiple files at a time to one specific host using --files-from. I can't think of what might have changed to have caused this. Using rsync to transfer a single file to

rsync error messages always in English (= never translated)?

I want to recognize and handle some rsync error messages in my log files (containing also the --itemize-changes output) on different computers with different language/locale settings. Can I rely on rsync to create only English error messages to have a stable pattern to recognize? PS: In the

Re: rsync exit code 23 (partial transfer due to errors): List of possible reasons and how to ignore some?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Unfortunately, exit 23 litterally just means something else went wrong and might have scrolled off of the screen if you have rsync listing files (--verbose or --itemize_changes). Essentially, it is anything that doesn't have its own exit code. I

Re: rsync exit code 23 (partial transfer due to errors): List of possible reasons and how to ignore some?

On Thu, 2023-12-14 at 14:09 -0500, Kevin Korb wrote: > Unfortunately, exit 23 litterally just means something else went wrong > and might have scrolled off of the screen if you have rsync listing > files (--verbose or --itemize_changes). Essentially, it is anything > that doesn't have its own

rsync exit code 23 (partial transfer due to errors): List of possible reasons and how to ignore some?

I am trying to find a solution for the open source Linux software "Back In Time" (https://github.com/bit-team/backintime) where we evaluate the rsync exit code when taking a backup via rsync and inform the user that an error has occured. Questions: 1. Is there full list of possible reasons

Re: rsync checksum inquiry

For example, is there any reason why rsync doesn't support blake2b( on 64b engines ) and blake2s ( on "tiny" engines )? On Sun, Oct 29, 2023, 5:49 p.m. brent kimberley wrote: > Hi. > What is the process for deciding what types of checksums can be included > with rsync? > > Best Regards, >

Re: rsync checksum inquiry

What is the process for deciding what types of checksums can be included with rsync? > -- 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:

Re: rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

Here is the missing attachment ;-) On Fri, 2023-09-22 at 21:01 +0200, rsync--- via rsync wrote: > On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote: > > So I decided to do a quick test using the Linux kernel source tree since > > it has lots of files. > > Excellent idea using kernel

Re: rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote: > So I decided to do a quick test using the Linux kernel source tree since > it has lots of files. Excellent idea using kernel sources! A lot of different files... I will use this to create indicative benchmarks for different scenarios... >  

Re: rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

On Fri 22 Sep 2023, Kevin Korb via rsync wrote: > 444 {} +' to make read only files for rsync to want to chmod, then used cp > -al to make several duplicate trees using hard linked files. An rm -rf on > one such tree took .97 seconds while an rsync deletion took 1.25 seconds. Be sure to drop

Re: rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

So I decided to do a quick test using the Linux kernel source tree since it has lots of files. I duplicated a tree, used 'find . -type f -exec chmod 444 {} +' to make read only files for rsync to want to chmod, then used cp -al to make several duplicate trees using hard linked files. An rm

Re: rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

On Thu, 2023-09-21 at 20:08 -0400, Kevin Korb via rsync wrote: > I have heard in the past that rsyncing an empty dir over a tree to > delete the tree is faster than an rm -rf but I can't say I have ever > benchmarked it to get any actual numbers. This **may** indeed be a myth (for a long time

Re: rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

I had intended to come back to this but because I didn't really think I had anything to add to the discussion I put it at a low enough priority that I forgot about it. But I saw your bug report and was surprised to see that I was already unhelpful on this topic but because that original

[Bug 12806] Deleting in a row of hardlinked snapshots resets file permissions.

https://bugzilla.samba.org/show_bug.cgi?id=12806 --- Comment #7 from Aryo Da --- I think this a severe bug for all backup use cases of rsync that take a full snapshot with permissions (--perms) by creating hardlinks to unchanged files + copies of changed files (--link-dest): -> Whenever an old

[Bug 12806] Deleting in a row of hardlinked snapshots resets file permissions.

https://bugzilla.samba.org/show_bug.cgi?id=12806 --- Comment #6 from Aryo Da --- Created attachment 18117 --> https://bugzilla.samba.org/attachment.cgi?id=18117=edit MRE (minimal reproducible example) as bash script to reproduce the bug Rename to "setup.sh" and make it executable... -- You

rsync --delete with empty source folder for fast snapshot deletion: Permissions of hardlinked files are changed to 644. Workaround?

Context --- I am one of the active developers of the open source application "Back in Time" which uses "rsync" as backend and I want to fix an open issue: "Back in Time"-Bug: https://github.com/bit-team/backintime/issues/994#issuecomment-1724211507 "Back in Time" uses "--link-dest"

Re: Feature Concept: enable iCloud Drive with rsync

Is this being accessed via a fuse mount? If so it seems like that is where this kind of feature should be implemented (like a mount option to decide how to handle such files). Rsync shouldn't need special features to deal with every kind of file storage. On 9/12/23 05:22, Brian "bex"

Feature Concept: enable iCloud Drive with rsync

Hi, I have also posted this on GitHub but it isn’t clear that was the right place: https://github.com/WayneD/rsync/issues/522 iCloud Drive will evict files that are unused or when additional space is needed on the local drive. The evicted files are replace by "bookmark" files that allow MacOS

Re: Why try to update (some) permissions which are the same?

Am 06.09.23 um 08:49 schrieb Paul Slootman via rsync: The current version is 3.2.7, especially 2.6.8 is quite ancient. You may want to upgrade before going bug hunting, chances are your problem has already been fixed. Oh yes, exactly the step to 3.* did a lot both to option and PERFORMANCE!

Re: Why try to update (some) permissions which are the same?

On Sun 03 Sep 2023, Perry Hutchison via rsync wrote: > On the source system: > > $ rsync --version > rsync version 2.6.8 protocol version 29 > On the destination system: > $ rsync --version > rsync version 3.0.7 protocol version 30 The current version is 3.2.7, especially 2.6.8 is quite

Re: Why try to update (some) permissions which are the same?

Kevin Korb wrote: > On Sun, 3 Sep 2023, Perry Hutchison via rsync wrote: > > On the source system: > > ... > > $ ll -d fcst-200[89] fcst-201[01] > > dr-xr-xr-x 2 perryh perryh 7168 Nov 27 2009 fcst-2008 > > dr-xr-xr-x 2 perryh perryh 9216 Jul 21 2010 fcst-2009 > > drwxr-xr-x 2 perryh

Re: Why try to update (some) permissions which are the same?

You have --itemize-changes but either it didn't or you filtered it out. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc.

Why try to update (some) permissions which are the same?

On the source system: $ rsync --version rsync version 2.6.8 protocol version 29 Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others. Capabilities: 64-bit files, socketpairs, hard links, ACLs, symlinks, batchfiles, inplace, IPv6, file

sync based on filename

Hello, I need to sync SRC to DST, but: - not based on file modification times - and not based on filesize + but on filename. Ie if this is current state, then sync: /SRC/2023-08-21 /DST/2023-08-19 but not if /DST contains newer directory (by name, not by modification time) so, imagine

Re: print only first level directory name when copying files

find /mnt/foo/* -maxdepth 0 -print -exec rsync -an `realpath {}` /mnt/bar/ \; (realpath eliminates the trailing slashes) On 8/3/23 22:27, Fourhundred Thecat via rsync wrote: Hello, I am copying /mnt/foo to /mnt/bar/   rsync --info=name1,del2 -rl /mnt/foo /mnt/bar/ /mnt/foo contains deep

Re: print only first level directory name when copying files

> On 2023-08-04 06:13, Perry Hutchison wrote: Perry Hutchison via rsync wrote: On second thought, that grep will match any directory name having 3 *or more* levels. This: rsync --info=name1,del2 -rl /mnt/foo /mnt/bar/ | egrep '^/[^/]*/[^/]*/[^/]*/$' should match only those with exactly

Re: print only first level directory name when copying files

Perry Hutchison via rsync wrote: > Fourhundred Thecat via rsync <400the...@lists.samba.org> wrote: > > > I am copying /mnt/foo to /mnt/bar/ > > > >rsync --info=name1,del2 -rl /mnt/foo /mnt/bar/ > > > > /mnt/foo contains deep directory structure, ie: > > > >/mnt/foo/aaa/ > >

Re: print only first level directory name when copying files

Fourhundred Thecat via rsync <400the...@lists.samba.org> wrote: > I am copying /mnt/foo to /mnt/bar/ > >rsync --info=name1,del2 -rl /mnt/foo /mnt/bar/ > > /mnt/foo contains deep directory structure, ie: > >/mnt/foo/aaa/ >/mnt/foo/aaa/somestuff/ >/mnt/foo/aaa/somestuff/file1 > >

print only first level directory name when copying files

Hello, I am copying /mnt/foo to /mnt/bar/ rsync --info=name1,del2 -rl /mnt/foo /mnt/bar/ /mnt/foo contains deep directory structure, ie: /mnt/foo/aaa/ /mnt/foo/aaa/somestuff/ /mnt/foo/aaa/somestuff/file1 /mnt/foo/bbb/ /mnt/foo/bbb/someotherstuff/

Consider POSIX_FADV_NOREUSE?

Hey rsync, Seems like there was an effort a while back to make use of POSIX_FADV_DONTNEED on linux [1]. Though the linux patches landed, apparently the rsync ones never did. Over a decade later we live in a different world. Linux is using the new-ish MGLRU on many distros, and (~6.3+) even has

Re: How to tune rsync to speed up?

NFS is slowing things down even more than your bandwidth measurements as it is also forcing --whole-file. On 8/2/23 05:03, Perry Hutchison via rsync wrote: Sebastian G??decke via rsync wrote: We're facing some flapping traffic when rsyncing atm 70T from one server to an DELL Isilon. Both

Re: How to tune rsync to speed up?

Sebastian G??decke via rsync wrote: > We're facing some flapping traffic when rsyncing atm 70T from > one server to an DELL Isilon. > Both systems are connected with 10G Fiber (not Channel). > So we started with one simple "rsync -a /src /dest" to the DELL > by using NFS3. > ... > I always

How to tune rsync to speed up?

Hi there, we're facing some flapping traffic when rsyncing atm 70T from one server to an DELL Isilon. Both systems are connected with 10G Fiber (not Channel). So we started with one simple "rsync -a /src /dest" to the DELL by using NFS3. So it runs with around 3Gbit for some seconds, than it were

Interaction between hosts allow and hosts deny

I am trying to master the hosts allow module parameters described by man rsyncd.conf . Quoting from the man page: > hosts allow > This parameter allows you to specify a list of comma- and/or > whitespace-separated patterns that are matched against a connecting client's > hostname and IP

[Bug 7809] I/O errors other than IOERR_GENERAL should not suppress deletion

https://bugzilla.samba.org/show_bug.cgi?id=7809 --- Comment #6 from Jeffrey Simon --- 3. The script does not work from launchd running as root. I should have given the failure mode, which is the following: rsync: opendir "/Volumes/Backup1/." failed: Operation not permitted (1) rsync error:

[Bug 7809] I/O errors other than IOERR_GENERAL should not suppress deletion

https://bugzilla.samba.org/show_bug.cgi?id=7809 --- Comment #5 from Jeffrey Simon --- "Excludes are relative to the source dir". Are you saying that the excludes should be --exclude=.DocumentRevisions-V100 --exclude=.TemporaryItems --exclude=.Trashes? That is a rhetorical question, because I no

[Bug 7809] I/O errors other than IOERR_GENERAL should not suppress deletion

https://bugzilla.samba.org/show_bug.cgi?id=7809 --- Comment #4 from Kevin Korb --- Your excludes aren't working because excludes are relative to the source dir not /. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid

[Bug 7809] I/O errors other than IOERR_GENERAL should not suppress deletion

https://bugzilla.samba.org/show_bug.cgi?id=7809 --- Comment #3 from Jeffrey Simon --- One other point to follow up my first post of 2023-07-21: None of these issues occurred on macOS Monterey 12.4.x -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use

[Bug 7809] I/O errors other than IOERR_GENERAL should not suppress deletion

https://bugzilla.samba.org/show_bug.cgi?id=7809 --- Comment #2 from Jeffrey Simon --- This is an old ticket, but I am getting the same or similar problem in 2023 with rsync on macOS Ventura 13.4.1. Here is the first attempt and partial results: rsync -av --delete /Volumes/Backup1/

Re: Local --fake-super restore failing(?) and creating local directories instead

On 2023-07-15 6:15 am, Zachary Vance via rsync wrote: I am on rsync version 3.2.7 protocol version 31, currently on an Arch Linux. The following seems I would expect to copy the contents of 'a' to 'c', based on my understanding of the the advice of `man rsync`: - mkdir a b c touch

Local --fake-super restore failing(?) and creating local directories instead

I am on rsync version 3.2.7 protocol version 31, currently on an Arch Linux. The following seems I would expect to copy the contents of 'a' to 'c', based on my understanding of the the advice of `man rsync`: - mkdir a b c touch a/hello rsync -M--fake-super -a a/ b/ rsync --super

Is this the best way to combine --times and --link-dest along with a de-duplicator?

I'm copying files using --link-dest to avoid duplication. I'm also using a de-duplicator (rmlint) to further reduce duplication. For files that are duplicates, I've rmlint set to use the timestamp of the oldest file. This ends up with starting conditions where the source of a copy might have

[PATCH] Add option --log-after to log after moving file into place

This mode is useful when a process is monitoring the log for post-processing of transferred files. With --log-after in local mode, both sender and receiver log to the same log file, so it require --log-file with absolute path. We add %o to the default log format, so it will be easy to tell the

Re: Rsync sends again already existing files

You should also read about --inplace. Without it --no-whole-file you are telling it to do all the extra data diffing only to write out an entire new file anyway (just using data from source and target to create it). On 6/30/23 21:29, Selva Nair via rsync wrote: So this disable a lot

  1   2   3   4   5   6   7   8   9   10   >