t use -a and instead use the remaining
> combination of options explicitly, or use --no-p.
>
> See the man page, specifically the sections for --perms and -a.
When I stepped this through the debugger I found that this was not the case.
The flaw is on this line:
https://github.com/Rs
On Tue, Apr 08, 2025 at 12:54:24PM +0100, Graham Leggett via rsync wrote:
> I misunderstood the --chmod option, thinking that it specified the
> permissions at the destination. What actually happens is that it
> overrides the source permissions, and has a side effect of the
>
On 08 Apr 2025, at 12:54, Graham Leggett via rsync
wrote:
> Another thing I've found is that my backups have lost their permissions.
>
> I misunderstood the --chmod option, thinking that it specified the
> permissions at the destination. What actually happens is that it
https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Due to some regressions in 3.4.0 we have released 3.4.1.
See https://download.samba.org/pub/rsync/NEWS#3.4.1 for details of the
changes
Our apologies for not catching these issues before 3.4.0
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change
Thanks for the advice. Unfortunately I tried:
--link-dest=/snapshots/rsync_test/last
and it still does not find it.
On Sun, Jan 12, 2025 at 8:37 AM Paul Slootman via rsync
wrote:
>
> On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote:
>
> > Thanks for your quick response. The r
On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote:
> Thanks for your quick response. The rsyncd.conf file looks like:
>
> charset = utf-8
> [user]
> path = /c/user
> comment = ""
> use chroot = true
Note the chroot... So "/" equals /c/user
&g
On 12.01.25 03:52, Anthony LaTorre via rsync wrote:
$ rsync -aPh --link-dest=/user/snapshots/rsync_test/last
/home/user/rsync_test
rsync://admin@readynas.internal/snapshots/user/Jan_11_2025
Password:
sending incremental file list
--link-dest arg does not exist: /user/snapshots/rsync_test/last
IX path is:
/c/user/snapshots/rsync_test/last
I've tried:
--link-dest=snapshots/rsync_test/last
--link-dest=./snapshots/rsync_test/last
--link-dest=../last
but none seem to work.
Thanks,
Tony
On Sat, Jan 11, 2025 at 9:02 PM Kevin Korb via rsync
wrote:
>
> rsyncd doesn't t
rsyncd doesn't take unix paths. You must adapt your --link-dest to
contend with however the rsycd module is defined in rsyncd.conf.
On 1/11/25 9:52 PM, Anthony LaTorre via rsync wrote:
Hi all,
I'm trying to figure out why a script works when using SSH but not
when using the rsyn
Hi all,
I'm trying to figure out why a script works when using SSH but not
when using the rsync protocol. When I run the following command:
rsync -aPh --link-dest=/user/snapshots/rsync_test/last
/home/user/rsync_test
root@readynas.internal:/user/snapshots/rsync_test/Jan_11_2025
it
On 24.12.24 09:53, Mario Marietto via rsync wrote:
There are times when a large file is copied up to 99% and then deleted after
having received the error. Other times when the error occurs earlier and only a
part of it is copied. Does it make sense to calculate the checksum if in both
cases
s: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>
> https://stackoverflow.com/questions/478722/what-is-the-best-way-to-calculate-a-checksum-for-a-file-that-is-on-my-machine
>
> On Mon, Dec 23, 2024 at 11:02:21PM +0100, Mario Marietto via rsync wrote:
> > -> Are you running windows on the same hardware as Linux/BSD ? Is it
If you have different systems for windows vslinux, it's possible there is
> a HW issue with one of them.
>
>
> Tom
>
>
> On 24 December 2024 7:44:16 am GMT+12:00, Mario Marietto via rsync <
> rsync@lists.samba.org> wrote:
>
>> What would you think if I t
Mario,
Are you running windows on the same hardware as Linux/BSD ? Is it a dual-boot
system?
If you have different systems for windows vslinux, it's possible there is a HW
issue with one of them.
Tom
On 24 December 2024 7:44:16 am GMT+12:00, Mario Marietto via rsync
wrote:
> Wh
-> Did you re-read the data and compare checksums ?
Don't know how to do this.
-> 2nd thought: What file systems do you use, and is there a peculiar size
of the file, hitting a limit?
Do I read this correct, rsync throws the error at
320,072,933,376, then continues to
640,302,152,539
On 23.12.24 20:44, Mario Marietto via rsync wrote:
What would you think if I told you that using Windows I no longer had that
problem ?
Would you still think that there are hardware problems ?
And if so, why would they only manifest themselves using Linux and FreeBSD and
not using Windows
ng Windows 11 because I want
> to
> > > exclude some variables from the equation.
> > >
> > > On Mon, Dec 23, 2024 at 7:49 PM Robin Lee Powell <
> > > rlpow...@digitalkingdom.org> wrote:
> > >
> > >> Almost certainly your drive is going ba
On Linux I'd tell you to
>> check dmesg for drive errors, I don't know what the FreeBSD
>> equivalent is. But I strongly recommend that you treat that drive
>> as "going to fail any second".
>>
>> On Mon, Dec 23, 2024 at 12:56:09PM +0100, Mario Mari
ivalent is. But I strongly recommend that you treat that drive
> as "going to fail any second".
>
> On Mon, Dec 23, 2024 at 12:56:09PM +0100, Mario Marietto via rsync wrote:
> > Using the parameters below the file hasn't been removed at 100% even if I
> > got the
Using the parameters below the file hasn't been removed at 100% even if I
got the same error :
root@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
--inplace --append --partial Free
BSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD
rsync: [sender] read e
Happened again :
root@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# sudo rsync
-azvvP FreeBSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD
sending incremental file list
delta-transmission disabled for local transfer or --whole-file
FreeBSD-141-UFS-sdc-DarkMatter.img
>As it's just a single file you're trying to copy, why not use cp?
>Although I expect that cp will also throw an IO error at some point.
Yes,I tried cp and I got the same error,that usually happens before
rsync,that is able to complete the transfer until 99%.
I've detached a
On Mon 23 Dec 2024, Mario Marietto via rsync wrote:
>
> Everytime I try to copy a file from one USB disk to another one (does not
> matter which one),I get this kind of error :
>
>
> mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
> -avxHAX
Hello.
Everytime I try to copy a file from one USB disk to another one (does not
matter which one),I get this kind of error :
mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
-avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.img
/mnt/sdj1/OS/Backup/BSD/FreeBSD --ignore-existing
k/mac/
On Fri, Nov 15, 2024 at 04:08:27PM +, Maxim Usatov via rsync wrote:
Dear All,
Having weird rsync issues after upgrading FreeBSD from 13.2 to 14.1 and
rsync along with it. I cannot find any solution. Setup: doing rsync backup
from the root ZFS to an SSD mounted to /media/da0p1. The rsy
On Sat, Nov 16, 2024 at 08:26:47AM GMT, Maxim Usatov via rsync wrote:
> Tried without nice, xattrs, acls and hard-links - same error.
Hmm okay, a real bug then :-) It likely has to do with the way cron
assumes the identity of the crontab owner. I would ask on the
freebsd-questions list. It
Hi Ian,
Tried without nice, xattrs, acls and hard-links - same error.
Regards,
Maxim Usatov
On 11/15/24 17:42, Ian Z via rsync wrote:
On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote:
I assume code 13 is related to permissions, but given rsync is
started as root, why
On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote:
> I assume code 13 is related to permissions, but given rsync is
> started as root, why would this happen? The same rsync commands
> worked on all previous versions of FreeBSD. It also fails with the
> same error
Dear All,
Having weird rsync issues after upgrading FreeBSD from 13.2 to 14.1 and
rsync along with it. I cannot find any solution. Setup: doing rsync
backup from the root ZFS to an SSD mounted to /media/da0p1. The rsync is
initiated as root using /etc/crontab. The log:
2024/11/15 08:30:01
Paul Slootman via rsync wrote:
> On Wed 16 Oct 2024, Chris Green via rsync wrote:
> >
> > I use it almost exclusively on Linux systems and it would be really
> > handy if I could set a number of options which would always be used
> > when I run rsync. These would be
On Wed 16 Oct 2024, Chris Green via rsync wrote:
>
> I use it almost exclusively on Linux systems and it would be really
> handy if I could set a number of options which would always be used
> when I run rsync. These would be in addition to -a which is useful
> but not quite
On Wed 09 Oct 2024, McDowell, Blake via rsync wrote:
> Linux servers one running TrueNAS-13.0-U6 and the other running
> TrueNAS-13.0-U3.1.
>
> I connect to both on a Mac via smb over fiber.
>
> Using cp -a also updates the timestamp of the copied file to today and does
>
conservator/archivist, so I
may be missing something obvious.
-Blake
From: Kevin Korb
Date: Wednesday, October 9, 2024 at 15:01
To: McDowell, Blake , rsync@lists.samba.org
Subject: Re: Question About Rsync and Modification Times
External Email - Exercise Caution
That isn't how rsync s
That isn't how rsync should work with -a. Is something preventing it
from backdating the file? What is the filesystem? Can you try copying
your 2015 file with cp -a?
On 10/9/24 14:56, McDowell, Blake wrote:
Hi Kevin,
The -a flag in this instance is not back-dating the timestamp o
transfer. I have a source file the has
a modification date of 2015 and when I rsync it to day with -a the copied file
has a modification date of today.
Again, this only happens on files that I use rsync to copy for the first time
over to empty storage. If I drag and drop the timestamp stays the same as
You are using rsync -a which copies (preserves) the timestamp. Meaning
that rsync will copy the file then back-date it to the timestamp of the
source file. Most copying tools do not do this though cp's -a does it
too. Note that your itemized output says that the timestamp is
diff
Hello,
I have a question about how/why rsync updates modification times, which I
haven’t been able to find an answer to.
I have two locally connected storage devices running TrueNAS Core: one is new
and empty, while the other is filled with files.
When I run the following rsync command
Hello,
I'm using rsync on RISC-V machines. I notice that the developers of
rsync seem to assume that only x86 CPUs can handle memory misalignments:
```c
/* We know that the x86 can handle misalignment and has the same
* byte order (LSB-first) as the 32-bit numbers we transmit. */
#if de
On Tue, Jul 16, 2024 at 05:56:28PM +0200, francis.montag...@inria.fr wrote:
> Hi.
>
> On Tue, 16 Jul 2024 16:00:47 +0100 Chris Green via rsync wrote:
>
> > I run a daily backup using 'rsync -a -F '
>
> > I want to exclude everything in ~/.local/share
On Tue, 16 Jul 2024 11:12:54 -0700 Ian Z via rsync wrote:
> On Tue, Jul 16, 2024 at 05:56:28PM GMT, Francis.Montagnac--- via rsync wrote:
>> No. Assuming you are doing this backup from your homedir, you should
>> add to your .rsync-filter file:
>> + /.local/
On Tue, Jul 16, 2024 at 05:56:28PM GMT, Francis.Montagnac--- via rsync wrote:
> > I want to exclude everything in ~/.local/share **except** the file:-
> >/home/chris/.local/share/evolution/calendar/system/calendar.ics
> > I have the following in my rsync-filter file t
Hi.
On Tue, 16 Jul 2024 16:00:47 +0100 Chris Green via rsync wrote:
> I run a daily backup using 'rsync -a -F '
> I want to exclude everything in ~/.local/share **except** the file:-
>/home/chris/.local/share/evolution/calendar/system/calendar.ics
> I have the
I run a daily backup using 'rsync -a -F '
I want to exclude everything in ~/.local/share **except** the file:-
/home/chris/.local/share/evolution/calendar/system/calendar.ics
I have the following in my rsync-filter file to exclude ~/.local/share
- .local/share
Can I simp
On Tue, Jul 09, 2024 at 11:37:19AM GMT, BP25 via rsync wrote:
> In other words, the recursion did not happen linearly (according to
> the tree structure of either the sender or the receiver). This is
> very counter-intuitive: I'd expect that every line which lies
> between any
Also note the SORTED TRANSFER ORDER paragraph in the rsync
manual. I don't think this paragraph is relevant to my question because
I understand it's only relevant to multiple nonrecursive rsync commands;
whereas I have one single recursive rsync command.
--
Please use reply-al
"atypical folders" be created in the middle of the recursion
"A/B/...", rather than together with the empty folder "A/B/" immediately
after rsync enters folder "A", and before rsync starts dealing with
files inside "A/B/"?
--
Please use reply
Dear rsync community,
I hope that someone can help me with this issue, probably
related to my lack of understanding of how rsync recursive works. In the
output was displayed something like this (I don't remember in the lines
below whether rsync was deleting or creating fil
https://bugzilla.samba.org/show_bug.cgi?id=3693
--- Comment #12 from Ben Millwood ---
hi folks, I've run into this problem in a couple of cases that I think haven't
been mentioned so far:
- Every month I rsync my boot disk to an external disk and then take a ZFS
copy-on-write snaps
Paul Slootman via rsync wrote:
> On Sun 02 Jun 2024, Chris Green via rsync wrote:
>
> > I have an rsync daemon running on a 64-bit (x86_64) system which I
> > successfully use for backups from several other 64-bit systems on my
> > LAN.
> >
> > I want to
On Sun 02 Jun 2024, Chris Green via rsync wrote:
> I have an rsync daemon running on a 64-bit (x86_64) system which I
> successfully use for backups from several other 64-bit systems on my
> LAN.
>
> I want to use it for backups from a BeagleBone Black (32-bit, armv7l)
> but i
I have an rsync daemon running on a 64-bit (x86_64) system which I
successfully use for backups from several other 64-bit systems on my
LAN.
I want to use it for backups from a BeagleBone Black (32-bit, armv7l)
but it fails as follows:-
root@bbb:~# rsync -a /etc chris@backup::bbb
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 i
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
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 laug
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
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
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
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,
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
> https://lists.sa
ve 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 protocol version 31
> Capabilities:
> 64-bit files, 64-bit inums, 64-b
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.
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
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'
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
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 (
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, p
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 con
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 conta
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
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
creenshot. errs was
definitely the one I referenced, and it was increasing.
As it turns out, there was some kind of network configuration issue with my
network provider that caused this fscking problem.
I knew at some point it couldn't have been an rsync problem, but I also
wasn't sure
ud...@gmail.com>> wrote:
Hi,
On Wed, Dec 20, 2023 at 11:03 AM Kevin Korb via rsync
mailto:rsync@lists.samba.org>> 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
at 9:27 PM Alex wrote:
> Hi,
>
> On Wed, Dec 20, 2023 at 11:03 AM Kevin Korb via rsync <
> rsync@lists.samba.org> 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
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 u
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
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 sing
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
-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 cod
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&#x
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 possib
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
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: http://www.catb.org/~esr/f
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
narios...
> 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.
> [...]
> But also, I did not experience the problem you are describing.
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.
B
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 file
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 (f
m hearing
that rsync actually adds a bunch of pointless chmods to the process. Is
it still faster given this problem? If so maybe we should be trying to
investigate why rm is so slow. Otherwise, I would agree that an
optimization to not do a bunch of pointless chmods is a good idea. I
would su
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
&q
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
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 a
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.
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
> b
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 second
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
>
> So this disable a lot of interest in Rsync :-( Isn't there a way to
> disable
> "--whole-file"?
>
"--no-whole-file" should do it though for local copies, forcing delta
transfer is not going to speed up anything in most cases.
Selva
--
Please use repl
Stephane Ascoet via rsync wrote:
> Kevin Korb le 29/06/2023 22:43:
> > Are you so sure rsync actually copies the file? It should
> > correct the timestamp and tell you it did.
>
> Of that what it should do! But I'm sure not: the target is a very
> low-quality-and
different and I don't really see why they
should go together.
I fully agree but I don't like long options ;-p
Are you so sure rsync actually copies the file? It should correct the timestamp
and tell you it did.
Of that what it should do! But I'm sure not: the target is a very
1 - 100 of 3554 matches
Mail list logo
