On 05 May 2025, at 20:14, Derek Martin wrote:
> If I understand correctly, I believe using --chmod without using
> --perms (or with --no-p) will do what you want. Typical command lines
> often use -a which equates to -rlptgoD (i.e. it includes -p/--perms).
> So you either need to not use -a and
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
> destination permission
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 overrides
> the source
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
On 23.12.24 22:06, Mario Marietto wrote:
-> Did you re-read the data and compare checksums ?
Don't know how to do this.
Files can be considered binary identical if they do have the same checksums.
e.g.
# md5sum [files]
Using windows:
https://windowsreport.com/checksum-on-windows/
c:certu
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 in output I don't have the same information that
there is
-> Are you running windows on the same hardware as Linux/BSD ? Is it a
dual-boot system?
I have a lot of disks connected to the PC (USB,Sata.M1,SSD) where I have
installed different OS,like Linux (Ubuntu 24.04),FreeBSD (14.1 and
14.2),Windows (11).
---> If you have different systems for windows
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:
> What would yo
-> 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 bytes (file
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?
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?
On Mon, Dec 23, 2024 at 9:38 PM Robin Lee Powell <
rlpow.
And I forgot to mention that I see the error even when trying to transfer
files from and to a new disk,not an USB disk,bought some days ago,model
Crucial BX500 SATA SSD 480GB,SSD. So,I'm not able to believe that even this
disk is damaged. This is a very strange situation.
On Mon, Dec 23, 2024 at
>Almost certainly your drive is going bad. 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".
I'm not sure that this is the reason. I see the error regardless of t
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 errors mapping
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
320,
>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 and reattached the USB d
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
> -avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.
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
> 16
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 ch
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
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 <
> shree
so it is more specific
> than "Re: Contents of rsync digest..."
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>
> ---
&g
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 a
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 a
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 lib/mod
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 t
> 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 was
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 er
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 fram
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 timeou
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 t
-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 jus
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 exit
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,
> Brent
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/faqs/
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 sources!
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...
>
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 the
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 -r
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 n
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
poster
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 of
>
> 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 reply-all for most replies to avoid omitting
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-performance USB key ... less tha
Kevin Korb le 29/06/2023 22:43:
-i, -v, and --progress all only affect the output.
Bonjour, of course I know ;-)
adds a header and footer and --progress of course adds the per-file
progress bar.
Thanks, that what I wanted to know, so I keep them all.
as those 2 options are very diff
Am 29.06.23 um 22:31 schrieb Stephane Ascoet via rsync:
Kevin Korb le 29/06/2023 04:52:
--itemize-changes will cause rsync to tell you what it thinks is
Hi, thank you so much! Today I used a little different way of doing it, and
another computer, and the behaviour is the same. It seems tha
On 6/29/23 16:31, Stephane Ascoet via rsync wrote:
Kevin Korb le 29/06/2023 04:52:
--itemize-changes will cause rsync to tell you what it thinks is
Hi, thank you so much! Today I used a little different way of doing it,
and another computer, and the behaviour is the same. It seems that the
Kevin Korb le 29/06/2023 04:52:
--itemize-changes will cause rsync to tell you what it thinks is
Hi, thank you so much! Today I used a little different way of doing it, and
another computer, and the behaviour is the same. It seems that the reason is a
different timestamp. So the whole file i
--itemize-changes will cause rsync to tell you what it thinks is
different. Also, -z is counter-productive when rsync isn't networking.
On 6/28/23 22:28, Stephane Ascoet via rsync wrote:
Hi, /media/clec1enextsanstampon/gigamopourcdas4/ contains an old copy of
files of /media/mo. I'm updating
Maybe the solution is explained here :
https://serverfault.com/questions/1110536/rsync-operation-not-supported-errors-for-acl-on-zfs/1110537#1110537
I tried to do something like this:
zpool import -f -R /mnt/zroot2 zroot2
zfs set acltype=posixacl zroot2/ROOT
why zroot2/ROOT ?
because :
# zfs
On 2023-03-09 09:10, Tomasz Chmielewski via rsync wrote:
So from the tests above, it hangs with rsync 3.2.3 on the sender and
rsync 3.2.7 on the receiver. I'll run some more tests.
Self-compiled rsync 3.2.7 on Debian to Ubuntu (rsync 3.2.7) - does NOT
hang.
Tomasz Chmielewski
--
Please us
On 2023-03-09 08:15, francis.montag...@inria.fr wrote:
Hi.
On Wed, 08 Mar 2023 22:21:28 +0100 Tomasz Chmielewski via rsync wrote:
After upgrading to rsync 3.2.7, the following command hangs forever
(using "--usermap" causes the hang; without "--usermap" it doesn't
hang):
rsync -v -p -e --us
Hi.
On Wed, 08 Mar 2023 22:21:28 +0100 Tomasz Chmielewski via rsync wrote:
> After upgrading to rsync 3.2.7, the following command hangs forever
> (using "--usermap" causes the hang; without "--usermap" it doesn't
> hang):
> rsync -v -p -e --usermap user:user /etc/services user@remote:
This
I got hit by that bug again, and this time I took the time to try to
create a minimal recipe. It turns out that the culprit was the -y flag,
which I had been using to save some bandwidth, but which doesn't work well
when there are "too many" files in a directory.
A simple reproducer (which
Hi Wayne,
As of this release, I cannot link rsync.
ERROR [1210]:
checksum.o: In function `csum_evp_md':
checksum.o(.text._158011632+0xe2): unresolved reference to EVP_MD_CTX_new.
This is on the NonStop ia64 and x86 platforms. Can you guide me?
Thanks,
Randall
Chris Green via rsync wrote:
> I have been using rsync to copy some web site files to a new (to me)
> hosting platform. Yesterday I was doing this and noticed that my ssh
> login to cPanel in another terminal window was unresponsive.
>
> On looking at the browser display of my cPanel admin windo
On Sun, Sep 18, 2022 at 6:13 AM Paul Slootman wrote:
> IMHO rsync is correct in refusing to run with a missing rsyncd.conf.
>
Yeah, it's one of the ways that some installs prevent a superfluous daemon
from starting up -- if it's not configured, you don't want it.
..wayne..
--
Please use reply-a
On Sat 17 Sep 2022, Colton Lewis via rsync wrote:
> This is on a system where /etc/rsyncd.conf does not exist and goes away if
> /etc/rsyncd.conf is an empty file.
>
> Version: rsync version 3.2.5 protocol version 31
> Command: rsync --daemon
> What happens: The program outputs "Failed to pars
there is connection timeout and I/O timeout
i'm using the I/O timeout.
for "--timeout" manpage is "if no data is transferredthen rsync will
exit"
no data is being transferred for hours, but it doesn't exit.
so, what's the problem here ?
--timeout=SECONDS
This option
You are using rsync over ssh. The connection timeout (and port) options
don't matter if rsync isn't doing the networking.
On 9/1/22 08:49, Roland via rsync wrote:
hello,
i do some backup via rsync/ssh and pull data from remote machine to
local machine.
whenever on remote machine there is som
I've definitely not seen that. If you can produce a working example
and tar it up for us to look at, that might be interesting/useful.
Just to check, though: you do not have --checksum/-c on, right?
On Sat, Aug 06, 2022 at 05:54:12PM +, Gregory Heytings via rsync wrote:
>
> I finally take t
On 02/08/2022 08:11, Wayne Davison wrote:
I have released rsync version 3.2.5pre1 for release testing. This
includes a checksum fix that affects some architectures (such as ARM),
improves the security of the received file list, enhances the manpage, etc.
I'd really appreciate it if people woul
чт, 28 июл. 2022 г. в 00:01, Alexander Gribanov :
> ср, 27 июл. 2022 г. в 16:55, :
>>
>>> On Wed, 27 Jul 2022 13:30:32 +0300 Alexander Gribanov via rsync wrote:
>>> > Rsync starts, goes as in the log below and just hangs like this for
>>> minutes
>>> > or maybe even hours and nothing changes...
>>
>
> ср, 27 июл. 2022 г. в 16:55, :
>
>> On Wed, 27 Jul 2022 13:30:32 +0300 Alexander Gribanov via rsync wrote:
>> > Rsync starts, goes as in the log below and just hangs like this for
>> minutes
>> > or maybe even hours and nothing changes...
>>
>> This may happen when windows is involved.
>>
>> Tr
Hello!
ср, 27 июл. 2022 г. в 16:55, :
> On Wed, 27 Jul 2022 13:30:32 +0300 Alexander Gribanov via rsync wrote:
> > Rsync starts, goes as in the log below and just hangs like this for
> minutes
> > or maybe even hours and nothing changes...
>
> This may happen when windows is involved.
>
> Try to
Hi.
On Wed, 27 Jul 2022 13:30:32 +0300 Alexander Gribanov via rsync wrote:
> Rsync starts, goes as in the log below and just hangs like this for minutes
> or maybe even hours and nothing changes...
This may happen when windows is involved.
Try to add the --whole-file option.
--
francis.monta
On Fri 24 Jun 2022, Kevin Korb via rsync wrote:
> Nope. Rsync groups are not groups of users they are just @users with their
> own password. I believe the @ just designates that you intend multiple
> people to have that password and use that username.
I think I have to disagree here.
The manpa
Nope. Rsync groups are not groups of users they are just @users with
their own password. I believe the @ just designates that you intend
multiple people to have that password and use that username.
On 6/24/22 12:34, Alexander Gribanov via rsync wrote:
Hello, Kevin! Thank You very much for th
Hello, Kevin! Thank You very much for the reply.
пт, 24 июн. 2022 г. в 19:00, Kevin Korb via rsync :
> I think you are thinking too much of rsync here. Rsync groups are the
> same as users they just have an @ in front of the name. If you want
> UNIX style users and groups then use rsync over ss
I think you are thinking too much of rsync here. Rsync groups are the
same as users they just have an @ in front of the name. If you want
UNIX style users and groups then use rsync over ssh and get the bonus of
ssh's authentication as well as not needing an rsyncd.conf file at all.
On 6/24/2
For those packaging rsync 3.2.4 using a C compiler where "char" defaults to
"unsigned char", such as ARM systems, rsync 3.2.4 will potentially generate
the wrong rolling checksum values, thus failing to optimize the copy with
the full amount of matching local data from a prior copy when high-bit
ch
On 29/10/21 11:07, Alessandro Baggi wrote:
Hi,
I'm using rsync in a script to perform backups (using hardlink). It
works very well. In my case I use an alternative output format to
retrieve md5hash for every synced file so that I can save the hash and
run an integrity check when needed. I u
--inplace can prevent rsync from running you out of disk space when
updating a large file. But you don't want to mix it with --update.
Judging by your other message you think that --update means modiify
files that are already on both ends. It doesn't. It only means that
rsync is forbidden to ch
‐‐‐ Original Message ‐‐‐
On Sunday, September 12, 2021 2:03 AM, Kevin Korb wrote:
> I thought I did elaborate. If it is a problem for you then maybe you
> shouldn't be using --update. Or you should let rsync delete incomplete
> files upon abort as it does by default.
I am using the follo
I thought I did elaborate. If it is a problem for you then maybe you
shouldn't be using --update. Or you should let rsync delete incomplete
files upon abort as it does by default.
On 9/11/21 9:29 PM, hancooper wrote:
> ‐‐‐ Original Message ‐‐‐
> On Saturday, September 11, 2021 11:20 PM,
--archive is all you really need. I actually wish --archive was the
default because it is all most people need and with the exception of
writing to a FAT filesystem it is almost always needed.
--append is for very special cases and should only be used if you really
know you need it and why. --ap
root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# tune2fs
-l /home/ziomario/Scrivania/antmicro/aosp_images/system-rw.img
tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name: /
Last mounted on:
/home/ziomario/Scrivania/antmicro/aosp_images/system-rw
Filesystem UUID:
root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# tune2fs
-l /dev/sda1
tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name:
Last mounted on: /
Filesystem UUID: 84d024e0-c8c7-42c0-ad3e-c3e0c1cacdb7
Filesystem magic number: 0xEF53
Filesystem revision #:1 (d
root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,nosuid,noexec,relatime,size=16338980k,nr_inodes=4084745,mode=755)
devpts on /
Those aren't really rsync errors they are just rsync telling you what
the kernel told it. The only thing I see wrong in your paste is that
you didn't use a trailing / on the source+target. Those do mean
something to rsync. The only thing I see wrong in the instructions is
the use of dd to make a
On Thu, 18 Feb 2021, 15:28 Karl O. Pinc via rsync,
wrote:
>
> For some 15 years+ (?) I've had a /root/.ssh/authorized keys line
> that starts with:
>
> "no-pty,no-agent-forwarding,no-port-forwarding,no-user-rc,no-X11-forwarding,command="rsync
> --server --daemon ."
>
> Occasionally I frob the ssh
On Thu 18 Feb 2021, Bri Hatch via rsync wrote:
>
> We use authprogs for more than just rsync though, and want more granularity
> than rrsync can support. If you force rrsync for the ssh key via
> command="rrsync" then that key may only be used to run rsync, you can't
> also allow additional comman
On Thu, 18 Feb 2021 12:22:33 -0500
Kevin Korb via rsync wrote:
> You should both look into rrsync. It comes with rsync and is designed
> to do exactly this.
I'm not really interested in restricting rsync to particular
directories. That seems to be what rrsync is for, although
it's a little h
I'm aware of rrsync, and it works well for its use case.
We use authprogs for more than just rsync though, and want more granularity
than rrsync can support. If you force rrsync for the ssh key via
command="rrsync" then that key may only be used to run rsync, you can't
also allow additional comman
You should both look into rrsync. It comes with rsync and is designed
to do exactly this. Unfortunately some Linux distros are maintained by
insane people who install rrsync as if it was documentation (compressed
and not executable) instead of a helper script which is what it is.
On 2/18/21 10:2
On Wed, 17 Feb 2021 21:52:06 -0800
Bri Hatch via rsync wrote:
> I recently added initial rsync support to authprogs.
> I'd be very interested in feedback
For some 15 years+ (?) I've had a /root/.ssh/authorized keys line
that starts with:
"no-pty,no-agent-forwarding,no-port-forwarding,no-user-
I am not sure if I have missed information here but... Rsync only sets
the mtime on files that it completely transferred. The back-dating of a
file is rsync's guarantee that that file was completely transferred and
verified.
On 2/2/21 9:03 PM, Leon Vanderploeg via rsync wrote:
> Windows Cygwin r
Windows Cygwin rsync is version 3.1.1
Ubuntu version is 3.1.2
Ubuntu file system is ext4
Rsync command main options -rtlg0D ( see attachment for full view)
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mail
In ,
on 01/24/21
at 07:46 PM, Leon Vanderploeg via rsync said:
Hi,
>rsync: failed to set times on "//.ImageTest.reg.jDGIg0":
>Invalid argument (22)
>Where is temp file coming from?
They are created to hold the content of the file to be replaced during the
data transfer. The names are chose
I think I found the problem.
Thanks to a ldd, I checked the libraries rsync is relying on and I found
out different versions for libxxhash between my two endpoints:
- on the target:
root@nas:~/sauvegardes-manuelles# dpkg -l libxxhash0
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
|
État
Either that or you have a hardware problem causing the checksum routine
to return the wrong result.
On 12/15/20 11:47 PM, Dan Stromberg via rsync wrote:
>
> On Tue, Dec 15, 2020 at 3:25 AM Laurent B via rsync
> mailto:rsync@lists.samba.org>> wrote:
>
> Dear all,
>
> I'm encountering a p
On Tue, Dec 15, 2020 at 3:25 AM Laurent B via rsync
wrote:
> Dear all,
>
> I'm encountering a problem with one of my backup. For some files, the
> checksum calculation is failing leading to the following error :
>
It sounds a little like a bug, but perhaps if you share the command you're
using fo
On Sun, Sep 27, 2020 at 12:27 PM Dipl.-Ing. Wolf-Dieter Pichler wrote:
> In this example output rsync says that it would just perform two
> group changes, BUT despite the -n option it actually synced some documents.
>
I doubt that very much, so I'd suggest checking on what else might be going
on.
+1
Original Message
On Sep 1, 2020, 10:44, Guillaume Bossu via rsync < rsync@lists.samba.org> wrote:
Hello,
First, thanks for your amazing job !
I used rsync on OSX on a 10Gbit network.
Now i move to 50Gbit network but rsync stay to a maximum transfert of 130 MB/s.
I believe tha
The obsd community is silent. There is a thread on misc@ but no participation.
Original Message
On 10 Aug 2020, 09:19, < pl...@agora.rdrop.com> wrote:
Rupert Gallagher wrote:
> ... I see this ball bounched betwen rsync, openbsd and supermicro
> ... I see a large cache delivered
Rupert Gallagher wrote:
> ... I see this ball bounched betwen rsync, openbsd and supermicro
> ... I see a large cache delivered by the OS on server hardware and
> a program unable to use it.
It sounds as if the problem may be OpenBSD "delivering" the cache
rather than "utilizing" it. What does
Beach ball play is fun, but I see this ball bounched betwen rsync, openbsd and
supermicro, and I am not enjoying it. I see a large cache delivered by the OS
on server hardware and a program unable to use it.
Original Message
On 8 Aug 2020, 20:14, < pl...@agora.rdrop.com> wrote:
Rupert Gallagher via rsync wrote:
> On 7 Aug 2020, 23:44, Wayne Davison < wa...@opencoder.net> wrote:
>
> >> Also, I have 12GB of cache in ecc ram that rsync is not using.
>
> >It uses whatever memory it needs plus whatever filesystem caching
> >your OS provides.
>
> Hmmm... bad day today...
>
>
Original Message
On 7 Aug 2020, 23:44, Wayne Davison < wa...@opencoder.net> wrote:
>> Also, I have 12GB of cache in ecc ram that rsync is not using.
>It uses whatever memory it needs plus whatever filesystem caching your OS
>provides.
Hmmm... bad day today...
No, it is not us
On Thu, Aug 6, 2020 at 10:46 PM Rupert Gallagher wrote:
> I noted that rsync writes a gmon file on the source path and leaves it
> there when it terminates.
Nope, it doesn't. You'll need to figure out what's going on with your
setup.
Also, I have 12GB of cache in ecc ram that rsync is not usin
1 - 100 of 4746 matches
Mail list logo
