Hi all,
I have one server hosting virtual machines and one older NAS Synology
DS1512+ used as backup target for those virtual machines. The NAS uses
BTRFS for its internal storage because I want to use compression and
at best make effecient use of snapshots.
When using "--inplace --whole-file"
Hello,
I am facing an issue when using --link-dest and --backup-dir together. When a
source file differs from the file in the destination directory and the --backup
and --backup-dir options are provided then a copy of the destination file is
made in --backup-dir. However, if additionally
On Mon, Nov 2, 2020 at 3:03 AM Manish Jain wrote:
> rsync -av --delete src dst # but protect dir dst/XYZ from deletion
>
> I tried "--filter 'protect dst/XYZ'" but that does not prevent the
> directory dst/XYZ from being deleted.
>
The "dst" dir isn't in the transfer, so it can't appear in a
Problem solved.
But I would like to know for my own sake if --delete can be made to work
while preventing a certain directory from deletion in the backup :
rsync -av --delete src dst # but protect dir dst/XYZ from deletion
I tried "--filter 'protect dst/XYZ'" but that does not prevent the
/mnt/sony is ext4. /mnt/wall is ext2.
I think I have spotted the problem. Let me try and work this out myself
now. If the problem persists, I will post again.
Thanks for your reply,
Manish Jain
On 2020-11-02 15:08, Kevin Korb via rsync wrote:
A few things here...
What filesystem is on
A few things here...
What filesystem is on /mnt/sony?
Add a --itemize-changes to see what it says is going on.
There really isn't a good reason to exclude lost+found. It should always
be empty and take up no space. If there is something in it that is a
sign that there is a problem with your
Hi,
I am facing a strange situation with my daily backups performed via
rsync. I primarily use Manjaro KDE Linux (LTS kernel), but also have
FreeBSD and Windows 10 bare-metal installations.
I have an all-OS-writable ext2 partition /dev/sda2 mounted at /mnt/wall
My USB backup device is a
The branch, master has been updated
via 286e164e Tweak cmd_txt routines in the packaging scripts.
from 85b8dc8a Force HAVE_LCHMOD off for Linux (for now).
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
discards b4d2b275562158c2ef971d4800286517536ccd87 (commit)
via 85b8dc8a Force HAVE_LCHMOD off for Linux (for now).
from b4d2b275 Force HAVE_LCHOWN off for Linux (for now).
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via b4d2b275 Force HAVE_LCHOWN off for Linux (for now).
via 07488001 Use the right powershell env syntax. [buildall]
from b7fab6f2 Allow cross-compilation with SIMD (x86_84) (#104)
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
You need to include the dirs leading to there...
--include=httpd/, --include=httpd/conf.d/
Otherwise it will never look inside to see the cluster.d
(I am assuming you are right about lsyncd using the same patterns as rsync).
On 10/21/20 9:01 AM, lejeczek via rsync wrote:
> hi guys,
>
> I'm
hi guys,
I'm trying lsyncd with some patterns which should be just
rsync's own patterns and I have these:
rsync = { _extra = {
"--include=samba**",
"--include=postfix**",
"--include=openvpn**",
"--include=strongswan**",
https://bugzilla.samba.org/show_bug.cgi?id=14529
--- Comment #1 from Andras Korn ---
It's completely fine if using this "database" in writable modules implies or
requires `max connections = 1` to avoid concurrency/locking issues.
--
You are receiving this mail because:
You are the QA Contact
https://bugzilla.samba.org/show_bug.cgi?id=14529
Bug ID: 14529
Summary: Please add option to save metadata to single file to
speed up backups
Product: rsync
Version: 3.2.0
Hardware: All
OS: All
The branch, master has been updated
via b7fab6f2 Allow cross-compilation with SIMD (x86_84) (#104)
via 9fc7deab Update CI builds to new path-setting idiom.
from b115bc8a Silence a few more warnings.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
Hi SMEs,
I have been working on a geo replication solution and it uses rsync
internally. Recently when I was running the utility in RHEL 8, I started
facing seeing the following message :
Popen: command returned error cmd=rsync -aR0 --inplace --files-from=-
--super --stats --numeric-ids
After more testing, I found that that command only syncs files that are in
that top dir. It doesn't recurse through all the dirs.
~
When you are principled, set standards and stick to them some people will
fall out of your life; let them!
My deepest apologies. I had an inotify running that anytime something was
added to that directory it would run a script that was doing my original
sync of pulling in all the directories and images. After turning that off,
I was able to see your line work as you said it should. Thank you very
Except some of those dir have subdir such as WhatsApp and DCIM has multiple
subdirs too. I would rather do it all with rsync though.
On Wed, Sep 30, 2020, 12:54 PM Wayne Davison wrote:
> On Tue, Sep 29, 2020 at 4:46 PM Rob Campbell wrote:
>
>> Thanks for your help. What you provided didn't
On Tue, Sep 29, 2020 at 4:46 PM Rob Campbell wrote:
> Thanks for your help. What you provided didn't work for me because that
> still placed things in subdirectories.
>
Ah, that's what you were trying to do. Your original email sounded like you
just didn't want it to recurse into
Interesting idea. It isn't something I have ever wanted to do. BTW, if
your find is recent use + instead of \;. + replaces {} with however
many entries fit in the command line length limit instead of running
individual rsync processes for each entry.
On 9/29/20 7:46 PM, Rob Campbell via rsync
Thanks for your help. What you provided didn't work for me because that
still placed things in subdirectories.
I figured it out. This puts it all in the images directory.
find /my/phone/root/dir/ \( -path '*Duo*' -o -path '*DCIM*' -o -path
'*Pictures*' -o -path '*Camera*' -o -path "*Download*"
The branch, master has been updated
via b115bc8a Silence a few more warnings.
via cd018c7a Use a better -Wno-pedantic heuristic.
from 9fce0eb5 Avoid some pedantic errors & old warnings.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via 9fce0eb5 Avoid some pedantic errors & old warnings.
via 33e94849 Handle early gcc versions that don't understand
-Wno-pedantic.
via 8f151118 Make gcc die on init overflow of an array.
via acca9d43 Expand the max name_num_item
On Sun, Sep 27, 2020 at 9:01 AM Madhu via rsync
wrote:
> Turns out the comment in rsync.h: (struct name_num_obj):
> struct name_num_item list[8]; /* A big-enough len (we'll get a
> compile error if it is ever too small) */
>
> isn't correct. I don't get a compile error.
Gcc likes to
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 Tue, Sep 29, 2020 at 7:38 AM Rob Campbell wrote:
> I would like to sync many subdirectories into one directory with no
> subdirectories. I've tried
>
> rsync -rv --progress --include '*.jp*g' --include '*.png' --include
> '*.dng' --include '*.raw' --include '*.nef' --include 'Duo' --include
>
On 9/29/20 7:07 AM, joe--- via rsync wrote:
> unknown module Linux1
This would imply that "Linux1" is not defined in the rsyncd.conf file on
the backup server. Of course since it is a NAS appliance I don't know
if you have any access to the config file.
1 check you could run is 'rsync
I am using the 'backup to a central backup server with 7 day
incremental' example to archive three separate computers to identically
configured (apart from name) shares on a Western Digital 'MyBookLive'
NAS which has rsync enabled. The backup from two Raspberry Pi Computers
operates without a
I would like to sync many subdirectories into one directory with no
subdirectories. I've tried
rsync -rv --progress --include '*.jp*g' --include '*.png' --include '*.dng'
--include '*.raw' --include '*.nef' --include 'Duo' --include 'DCIM'
--include 'WhatsApp' --exclude '*' /my/phone/root/dir/
On Sun, Sep 27, 2020 at 03:19:17PM -0700, Will McGinnis via rsync
wrote:
> Hello, A GUI program uses rsync for network transfers. It is able to
> load filters from a file by putting a dot and underscore before it.
> Example:mkdir 1 2; touch 1/a .empty; rsync -f ._empty 1/ 2/
>
> Is the dot
Hello, A GUI program uses rsync for network transfers. It is able to
load filters from a file by putting a dot and underscore before it.
Example:mkdir 1 2; touch 1/a .empty; rsync -f ._empty 1/ 2/
Is the dot underscore specific to rsync or is it a general bash (or
similar?) feature to load
Since Ubuntu 20.04 (focal) the rsync option -n (Dry Run) is not working
correctly.
---
rsync --version
rsync version 3.1.3 protocol version 31
I used this command for about ten years without mayor issues:
---
rsync -vaHEiuzn --skip-compress=jpg,JPG,mov,MOV,mp4,MP4,m4v,avi,png
With rsync-patches/md5p8.diff and --enable-xxhash
% gdb --args ./rsync --version
Using host libthread_db library "/lib64/libthread_db.so.1".
rsync version v3.2.3-29-ge55788bd protocol version 31
Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.
Web site:
On Thu, Sep 17, 2020 at 5:32 AM Matt McCutchen wrote:
> For the "not transfer" part, I can use --ignore-existing, but I don't see
> a direct way to be warned only about source files that differ from
> existing destination files.
>
Indeed, the 2-step approach that you mentioned is all that the
The branch, master has been updated
via 740ed11a Make the extra info on the "exists" messages optional.
from d2a97a7a Various file comparison improvements
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via d2a97a7a Various file comparison improvements
from 15bc7ded More NEWS updates.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
Nevermind this message. The issue is a platform utility malfunctioning. Not an
rsync issue.
Randall S. Becker, Managing Director, Nexbridge Inc.
+1.416.984.9826
From: Randall S. Becker
Sent: September 22, 2020 3:30 PM
To: 'rsync@lists.samba.org'
Subject: [Test Problem] RSync 3.2.3 -
Hi!
I’ve encountered a weird test failure at commit 15bc7ded
PASS00-hello
rm: cannot remove '... /testtmp/00-hello': Directory not empty
I have not seen this in prior commits. Any ideas on what I can look?
Thanks,
Randall
-- Brief whoami:
NonStop developer since
The branch, master has been updated
via 15bc7ded More NEWS updates.
via f0810068 A couple whitespace tweaks.
via 7aa2f363 optimize avx2 code (#102)
from 9cd85b84 Skip an append if sender's file gets shorter.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
-
The branch, master has been updated
via 9cd85b84 Skip an append if sender's file gets shorter.
via f8dcd7d4 Improve the docs for `--archive`.
via 69530b40 Avoid output variance in protocol 29.
via 122b0fdc Check status of tests that pipe rsync's output & simplify
Hi again, rsync list! I was heavily involved in rsync development and
support back in 2005-2010. I've largely lost interest in that now and
my knowledge of rsync is beginning to become stale, but I'm still a big
fan and user of rsync, so I'm back with a user question. :) I did
search the web
raf,
On 2020-09-14 10:07, raf via rsync wrote:
On Fri, Sep 11, 2020 at 10:53:14AM +1000, Philip Rhoades via rsync
wrote:
Roland,
On 2020-09-10 21:27, Roland wrote:
> > with rsync hanging - after breakout on /home for writing I then get:
> > "Read-only file system"
>
> if your filesystem
On Fri, Sep 11, 2020 at 10:53:14AM +1000, Philip Rhoades via rsync
wrote:
> Roland,
>
>
> On 2020-09-10 21:27, Roland wrote:
> > > with rsync hanging - after breakout on /home for writing I then get:
> > > "Read-only file system"
> >
> > if your filesystem switches to read-only, you have a
Roland,
On 2020-09-10 21:27, Roland wrote:
with rsync hanging - after breakout on /home for writing I then get:
"Read-only file system"
if your filesystem switches to read-only, you have a serious problem
with your system/storage, not with rsync.
rsync (or the workload) is simply triggering
>with rsync hanging - after breakout on /home for writing I then get:
>"Read-only file system"
if your filesystem switches to read-only, you have a serious problem
with your system/storage, not with rsync.
rsync (or the workload) is simply triggering the problem.
regards
roland
Am 10.09.20
People,
When I did:
rsync -av /home/ /mntb5/ # about 4TB
I got errors like:
'rsync [sender] expand file_list pointer array to xxx bytes, "did
move"'
with rsync hanging - after breakout on /home for writing I then get:
"Read-only file system"
So after unmounting and remounting
The branch, master has been updated
via a79d9b22 Update the NEWS.
via 2613c9d9 Handle a --mkpath failure
via 27aff880 Use new xxhash lib in cygwin build. [buildall]
via 7b53e67d Try using the Windows version of curl. [buildall]
via da956469 Another cygwin
The branch, master has been updated
via a35a900a Add git-version.h to "gen" target.
from f4c3969b Leave git-version.h out of GENFILES so it doesn't go in a
release tar.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via f4c3969b Leave git-version.h out of GENFILES so it doesn't go in a
release tar.
via ee75e51f Allow git-version.h to be provided for the build
from 9f9240b6 Set CXX_OK=no when cross compiling.
The branch, master has been updated
via 9f9240b6 Set CXX_OK=no when cross compiling.
via 48885309 Create SECURITY.md
via 203b3d01 Setup for 3.2.4dev.
via 25526eb3 Simplify the compat logic for local_server
from c3f7414c rsync-ssl: Verify the hostname in the
On Tue, Sep 1, 2020 at 8:43 PM Philippe Höij wrote:
> There is a security issue in rsync that needs to be disclosed to the team.
>
I added a security policy to the repo which indicates that security issues
can be emailed to me.
..wayne..
--
Please use reply-all for most replies to avoid
Hi,
There is a security issue in rsync that needs to be disclosed to the team.
Similar issues in other tools have CVEs of high severity assigned to them, and
rsync has such an issue as well.
I would like to enable the rsync maintainers to be aware of, and hopefully to
fix the issue. I know of
+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
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 that the limit comes from the read block size fixed at 256K.
Could it be changed to 512K or even to 1 000K to enjoy the
The branch, master has been updated
via c3f7414c rsync-ssl: Verify the hostname in the certificate when
using openssl.
from 4c4fce51 Add some comments about protocol versions.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
hi
currently i rsynced several tbytes of files / backups to other/newer drives
using fedora 32 x64.
- the data was on ext4 / ntfs drives before.
- the machine has 8GB ram and swap
- different external usb3 drives up to 10tb
bug:
- rsync to a exfat drive often halted leaving a defunct rsync
https://bugzilla.samba.org/show_bug.cgi?id=14463
--- Comment #4 from Wayne Davison ---
The pre-release patches aren't guaranteed to be backward compatible, and in
this case the bits that were used in a couple different patches actually
conflicted with each other. So, when --atimes was promoted
https://bugzilla.samba.org/show_bug.cgi?id=14463
--- Comment #3 from bumkick...@yahoo.com ---
It's not a trivial exercise to upgrade the rsync version on the target system,
so it would be useful if there was some kind of "back patch" available
| suspect there might be others with similar issues
https://bugzilla.samba.org/show_bug.cgi?id=14463
--- Comment #2 from bumkick...@yahoo.com ---
(In reply to Wayne Davison from comment #1)
What should we do instead to keep the same functionality?
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use
But it seems the files are the same. Is there another possible reason? Thanks.
On 8/11/20, Kevin Korb via rsync wrote:
> Mostly it means that the file rsync ended up with on the target end
> didn't match the file on the source it started with. This is mostly
> caused by the file being modified
Mostly it means that the file rsync ended up with on the target end
didn't match the file on the source it started with. This is mostly
caused by the file being modified on the source while rsync is copying
it but it can also be a memory corruption problem.
On 8/11/20 1:13 PM, Peng Yu via rsync
Hi,
I see some warnings like the following. Could anybody explains what
they mean? Thanks.
19/31274477.pdf
257,169,119 0%1.26MB/s0:03:15 (xfr#121,
to-chk=848309/1043298)WARNING: 18/32281577.pdf failed verification --
update retained (will try again).
WARNING: 19/28879866.pdf failed
https://bugzilla.samba.org/show_bug.cgi?id=14463
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=14463
Bug ID: 14463
Summary: rsync 3.2.2 server protocol error
Product: rsync
Version: 3.2.0
Hardware: All
OS: FreeBSD
Status: NEW
Severity: normal
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>
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
The branch, master has been updated
via 4c4fce51 Add some comments about protocol versions.
via 6816b313 Simplify where version.h is included.
from e94bad1c Preparing for release of 3.2.3
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
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
On Thu, Aug 6, 2020 at 11:48 PM Michal Ruprich wrote:
> I see that a couple of patches from the rsync-patches tar have
> disappeared, like acls.diff or xattrs.diff yet I don't see the changes in
> the code. Is there a reason for their removal?
>
Various things were removed that had limited value
Hi Wayne,
I see that a couple of patches from the rsync-patches tar have
disappeared, like acls.diff or xattrs.diff yet I don't see the changes
in the code. Is there a reason for their removal? Were they applied
differently on the code and are no longer needed?
Thanks for any info on this.
Rsync 3.2.2 ransfer rate on my pet hardware is really poor, so every
improvement counts.
I noted that rsync writes a gmon file on the source path and leaves it there
when it terminates. When the source path is read-only, rsync complains that it
cannot write in it. For optimal use of the input
I have released rsync 3.2.3. It contains a smattering of bug fixes and
various enhancements.
To see a summary of all the recent changes, visit this link:
https://rsync.samba.org/ftp/rsync/NEWS#3.2.3
You can download the source tar file and its signature from here:
I have released rsync 3.2.3. It contains a smattering of bug fixes and
various enhancements.
To see a summary of all the recent changes, visit this link:
https://rsync.samba.org/ftp/rsync/NEWS#3.2.3
You can download the source tar file and its signature from here:
The branch, master has been updated
via e94bad1c Preparing for release of 3.2.3
via 617d726a Tweak a comment.
from 020eda88 Change fetch depth.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
The annotated tag, v3.2.3 has been created
at 1a2d16c0bd161481cbf0acc06dceb1ce788f0d09 (tag)
tagging e94bad1c156fc3910f24e2b3b71a81b0b0bdeb70 (commit)
replaces v3.2.3pre1
tagged by Wayne Davison
on Thu Aug 6 20:58:52 2020 -0700
- Log
The branch, master has been updated
via 020eda88 Change fetch depth.
via b5f8021a Don't use --always to ensure a tag is in gitver.
via 7b694757 Avoid a build fail when git isn't installed.
via 9375a8c4 Make my_alloc(NULL) use malloc instead of calloc.
via
The branch, master has been updated
via dee09932 Create usage.c for smaller awk-dep rebuilds.
from 47351c2b Use RSYNC_GITVER in more output
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 47351c2b Use RSYNC_GITVER in more output
from 16b76706 A couple more mkgitver tweaks
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 16b76706 A couple more mkgitver tweaks
from 72b2a81f Use --abbrev=8 instead of --tags.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
Got it working properly. Many thanks!
Regards,
Matt Stevens
On 8/3/20 10:28 AM, Paul Slootman via rsync wrote:
On Mon 03 Aug 2020, Matt Stevens via rsync wrote:
So I've gotten excluding paths to work as a standalone command. When I paste
this into a script however, it ignores the exclusions.
On Mon 03 Aug 2020, Matt Stevens via rsync wrote:
> So I've gotten excluding paths to work as a standalone command. When I paste
> this into a script however, it ignores the exclusions. Any advice?
>
> rsync -aXvr --times --links
>
So I've gotten excluding paths to work as a standalone command. When I
paste this into a script however, it ignores the exclusions. Any advice?
rsync -aXvr --times --links
--exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'}
/home/path/ user@nas:/NAS/HOME/destination/
Are there
Hi Matt,
On Sat, Aug 01, 2020 at 10:10:49PM -0400, Matt Stevens via rsync wrote:
> I lack development skills. Would there be a way for rsync to be passed an
> option to exclude a specific path during a sync operaton? All of my attempts
> to use exclude have failed, as it does not respect paths,
Greetings. I've been using rsync for quite a long time. I have a homedir
I like to backup to a NAS. I find myself having to manually specifying
paths rather than letting rsync copy the entire home directory.
I lack development skills. Would there be a way for rsync to be passed
an option to
The branch, master has been updated
via 72b2a81f Use --abbrev=8 instead of --tags.
from d73c26d2 Put git version in a file for between-release versioning.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via d73c26d2 Put git version in a file for between-release versioning.
via e83bbeb6 Don't make .PHONY the first target in a Makefile.
from b6aa9c5c Make configure less annoying
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
-
The branch, master has been updated
via b6aa9c5c Make configure less annoying
from dfe3b77c Some Makefile improvements.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The disk is brand new.
Original Message
On 30 Jul 2020, 16:00, Karl O. Pinc < k...@meme.com> wrote:
On Thu, 30 Jul 2020 06:55:00 +
Rupert Gallagher via rsync wrote:
> I updated the archive disk, it is a 4T WD Red SSD, now copying from
> the old Seagate Exos. Speed is
I would not refer to it as consumer: it costs 670 eur, it is specifically
designed for nas, ans it comes with a 5 years warrantee.
Original Message
On 30 Jul 2020, 16:00, Karl O. Pinc < k...@meme.com> wrote:
On Thu, 30 Jul 2020 06:55:00 +
Rupert Gallagher via rsync wrote:
I updated the archive disk, it is a 4T WD Red SSD, now copying from the old
Seagate Exos. Speed is ridiculous: only 80GB copied overnight.
I need help here--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
The annotated tag, v3.2.3pre1 has been created
at c6574a7fb49cecd5f7fef40835200efec7febc7c (tag)
tagging 8695bcc2b140b2518254234659a03b96f04055fc (commit)
replaces v3.2.2
tagged by Wayne Davison
on Mon Jul 27 17:58:25 2020 -0700
- Log
The branch, master has been updated
via dfe3b77c Some Makefile improvements.
via cbe3b2bf Tweak a comment.
from b1ae7fc9 INSTALL changes, including some Fedora packages.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via b1ae7fc9 INSTALL changes, including some Fedora packages.
from 8695bcc2 Preparing for release of 3.2.3pre1
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
On Tue, Jul 28, 2020 at 4:43 PM Nelson H. F. Beebe via rsync <
rsync@lists.samba.org> wrote:
> xxhash in particular is not a package that we have needed before, so none
> of the clients has it.
>
All new, wonderful libraries have a point in time where they begin to get
used. If you transfer
So far on my NonStop platform boxes, the rsync 3.2.3pre1 looks stable
building off our git clone.
Regards,
Randall
-- Brief whoami:
NonStop developer since approximately 2112884442
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
--
Please use
> On 28 Jul 2020, at 20:53, Nelson H. F. Beebe via rsync
> wrote:
>
> To my surprise, ALL of the builds failed, and examination of the build
> logs showed they were all due to missing libraries or header files,
> notably for one or more of lz4, openssl, xxhash, and zstd. Once I
> installed
801 - 900 of 34724 matches
Mail list logo
