Here's a test for clone-test on bcachefs, also available here:
https://github.com/josephmaher/rsync
Notes:
Test needs to be run as root.
clone-dest-bcachefs needs mkfs.bcachefs
Joseph
On Wed, 14 Feb 2024, Joseph Maher via rsync wrote:
WayneD's clone-dest patch seems to
Hi,
thanks for the information. Shall I file a bug report at
https://github.com/RsyncProject/rsync/issues ?
Yours
lopiuh
Am Mo., 3. Juni 2024 um 15:57 Uhr schrieb Paul Slootman via rsync
:
>
> On Mon 03 Jun 2024, Kevin Korb via rsync wrote:
>
> > It appears that xattr changes (that is what the
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 use it for backups from a BeagleBone
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 it fails as
On Mon 03 Jun 2024, Kevin Korb via rsync wrote:
> It appears that xattr changes (that is what the x mens) never made it into
> the verbose output. I would call that a bug but I would rather it be fixed
> by making -v include -i.
I think -v only shows when file data is transferred (or files /
It appears that xattr changes (that is what the x mens) never made it
into the verbose output. I would call that a bug but I would rather it
be fixed by making -v include -i.
On 6/3/24 05:22, - via rsync wrote:
Hi,
Version: sync version 3.3.0 protocol version 31
If I do a
I get:
Hi,
Version: sync version 3.3.0 protocol version 31
If I do a
I get:
=
sending incremental file list
var/log/journal/
sent 263,31K bytes received 1,14K bytes 528,90K bytes/sec
total size is 294,92M speedup is 1.115,21 (DRY RUN)
=
including option <-i>:
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
>
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
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
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
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 <
>
mba.org/mailman/listinfo/rsync
> or, via email, send a message with subject or body 'help' to
> rsync-requ...@lists.samba.org
>
> You can reach the person managing the list at
> rsync-ow...@lists.samba.org
>
> When replying, please edit your Subject line so it i
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
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
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
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.
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
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
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
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 *
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
--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:
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
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
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
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
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.
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
> 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
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
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
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
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
-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
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
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,
>
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:
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
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
-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 now) re-cited again and again
long time now) re-cited again and again and
- could no longer be valid today
- could apply only when deleting explicitly named files but not deleting the
complete folder
(as we need to do in "Back in Time")
At least I could not find a holistic benchmark with many files and differe
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
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"
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!
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
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
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.
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
> 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
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/
> >
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
>
>
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
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
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
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 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
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
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
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
ec1enextsanstampon/gigamopourcdas4/ are re-sended from
/media/mo instead of being skipped, why?
--
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
Kevin Korb Phone:(407) 252-6853
Systems Administrator Internet:
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
You're probably right. I've spent too much time on this and it's not
working so.I quit.
*From:* Robin Lee Powell [mailto:rlpow...@digitalkingdom.org]
*Subject:* copy to destination only new files
*Date:* Saturday, June
* Albert Croft via rsync
:
Wrote on Sat, 3 Jun 2023 11:52:56 -0500:
> You say, "knocking my ssh session offline on all terminals and it
> blocks ssh from being able to connect again. Even restarting sshd
> doesn't help".
>
> Questions:
> * Is the network stack on the affected machine still
m=${exclude} --safe-links
> --itemize-changes --no-perms --no-owner --progress --stats \
> al...@labadmin-precision-tower-3620.montefiore.org
> <mailto:al...@labadmin-precision-tower-3620.montefiore.org>:/home/alexa/
> /mnt/data.einstein/luke/all_but_dat/alexa/desktop_bkup/prof
Thank you Kevin!
--partial --partial-dir {hidden relative_sub-dir} is perfect!
Interrupted files stay there until they complete.
Thanks
From: Kevin Korb
Sent: Wednesday, June 7, 2023 4:26 PM
To: Lacey, Nathan ; rsync@lists.samba.org
Subject: Re: [External] Re
a partial file that isn't hidden is worse.
Because any other app looking at the file would think the transfer is
complete and try to use it.
It doesn't need to be a orphaned file, when called next time with
--partial rsync could re-opened the incomplete/hidden file, than it
could continue
I'm suggesting a partial file that isn't hidden is worse.
Because any other app looking at the file would think the transfer is complete
and try to use it.
It doesn't need to be a orphaned file, when called next time with --partial
rsync could re-opened the incomplete/hidden file, than
That is what --partial does. It keeps the partial file. If it kept the
temporary file with the random file name that would just be a useless
orphaned file.
On 6/7/23 15:02, Lacey, Nathan via rsync wrote:
This is a clone from https://github.com/WayneD/rsync/issues/484
Maurice,
You say, "knocking my ssh session offline on all terminals and it blocks
ssh from being able to connect again. Even restarting sshd doesn't help".
Questions:
* Is the network stack on the affected machine still active? (Can it
reach other services or systems on the network?)
* If
Nice job on converting each switch to it's equivalent human readable format!
I used Gentoo for two decades or so. Now using Void Linux as I have
little time for compiling.
One item that might be noteworthy for those running Gentoo, or a
compiled from source distribution, is including reporting
the system it's running on, to the Gentoo
Linux system? Is the CIFS mount actually mounted on the Gentoo Linux, or
is the Gentoo Linux system serving the CIFS mount which actually is
mounted on the "one computer"? In that case it would be much better to
directly rsync to the filesystem
dmin-precision-tower-3620.montefiore.org:/home/alexa/
> /mnt/data.einstein/luke/all_but_dat/alexa/desktop_bkup/profile \
> >> /home/maurice/logs/rsync-client-alexa.log
>
> I re-ran the scripts skipping this one. The next one was running
> and during that period, ssh stopp
_dat/alexa/desktop_bkup/profile \
>> /home/maurice/logs/rsync-client-alexa.log
I re-ran the scripts skipping this one. The next one was running and during
that period, ssh stopped responded to new connections, so it may be the case
that the failure is taking place across time, and it doesn'
Maurice R Volaski via rsync wrote:
> I have an rsync script that it is copying one computer (over ssh)
> to a shared CIFS mount on Gentoo Linux, kernel 6.3.4. The script
> runs for a while and then at some point quits knocking my ssh
> session offline on all terminals and it blocks ssh from
On Fri, May 26, 2023 at 08:34:20AM -0700, Wayne Davison wrote:
> On Tue, May 16, 2023 at 2:03 PM Derek Martin wrote:
>
> > This appears to be because of a type mismatch between xfer_sum_len
> > (declared as [signed] int) and the third arugment to memset, whose
> > function prototype is (from the
On Fri, 26 May 2023, Wayne Davison wrote:
On Tue, May 16, 2023, Marc Aurèle La France wrote:
Similar to --omit-{dir,link}-times:
--omit-device-times omit device files from --times
--omit-special-times omit sockets and fifos from --times
I'm not convinced these are needed at present.
On Tue, May 16, 2023 at 7:28 PM Marc Aurèle La France wrote:
> Similar to --omit-{dir,link}-times:
>
> --omit-device-times omit device files from --times
> --omit-special-times omit sockets and fifos from --times
>
I'm not convinced these are needed at present.
Also, fix corner case that
On Tue, May 16, 2023 at 7:28 PM Marc Aurèle La France via rsync <
rsync@lists.samba.org> wrote:
> Device files should be counted as devices, not symlinks.
>
Thanks for the catch! I fixed this the other day.
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
On Tue, May 16, 2023 at 2:03 PM Derek Martin wrote:
> This appears to be because of a type mismatch between xfer_sum_len
> (declared as [signed] int) and the third arugment to memset, whose
> function prototype is (from the man page):
>
>void *memset(void *s, int c, size_t n);
>
If that
Don't know if this is enough for you, but it may help at least a bit to hunt
down your problem. There is a flag -i
From man rsync
--itemize-changes, -ioutput a change-summary for all updates
this gives either a "." for no change, or a letter code for each change in "data,
time, size"
The only way I know of to determine this behavior is to use the
--link-dest option in rsync OR use the much older cp -al then rsync over
top of it method. With --link-dest a change in the file's metadata
causes rsync to duplicate the file in order to store both versions of
the metadata. With
People,
On 2023-04-16 18:06, Philip Rhoades via rsync wrote:
People,
I have command for backing up to a backup dir (eg /home/backup/prix/)
with:
rsync -av --delete --link-dest /home/backup/prix/${1}_0_hard_link
/$1/ /home/backup/prix/${1}_$dt/
for example the etc dir - which creates the
Obviously self-promotional, but Parsyncfp?
https://github.com/hjmangalam/parsyncfp
There are other like scripted parallel rsyncs, but I like this one. ;)
Hjm
On Mon, Apr 17, 2023, 3:42 AM just subscribed for rsync-qa from bugzilla
via rsync wrote:
>
Roland via rsync (Sa 11 Feb 2023 20:04:18 CET):
> do you have performance comparison vs. plain fail on the same hardware
> setup ?
I digged a bit more, and the performance issue seems to be due to setup
on the receiver's side: btrfs on LVM on dm-crypt on md-raid5
So my bmapfs doesn't solve any
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
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
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:
Robin Lee Powell via rsync (Di 07 Mär 2023 16:20:39
CET):
> First of all, I disagree that rsync handles very large files badly,
> but that's not super relevant. :) Consdier --partial for large
> files.
I'm using --inplace (because the receiving side does snapshots of the
underlying file
Hi
On Sun, 05 Mar 2023 07:45:16 -0800 Robin Lee Powell via rsync wrote:
> Oh, yeah, I missed that part. Yeah, don't do that; it's easy to add
> a lock file to a shell script.
Not so easy IMO to do that properly. Use the flock command if your system
provides it.
That said, using a systemd
On Tue, Mar 07, 2023 at 01:16:07PM +0100, Heiko Schlittermann via rsync wrote:
> Robin Lee Powell via rsync (Di 07 Mär 2023 07:07:01
> CET):
> > Read the "PER-DIRECTORY RULES AND DELETE" of the man page. (And
> > don't feel bad, it took me a while to figure it out myself).
>
> I did, but
Hello Kevin,
Kevin Korb via rsync (Di 07 Mär 2023 00:01:27 CET):
> I am not 100% sure I am interpreting this correctly but I think you are
> complaining that the file was being deleted in the first command? If so,
> instead of -F try --include='*/' --exclude='*'. Otherwise, maybe you want a
>
Robin Lee Powell via rsync (Di 07 Mär 2023 07:07:01
CET):
> Read the "PER-DIRECTORY RULES AND DELETE" of the man page. (And
> don't feel bad, it took me a while to figure it out myself).
I did, but left with some uncertainty.
"H" hides the files from the transfer? What does it mean?
"P"
Read the "PER-DIRECTORY RULES AND DELETE" of the man page. (And
don't feel bad, it took me a while to figure it out myself).
Short version: per-directory rules only apply on the side they're
*specified on*, but you need the exclusion to apply to *both* sides.
The following works, for the
I am not 100% sure I am interpreting this correctly but I think you are
complaining that the file was being deleted in the first command? If
so, instead of -F try --include='*/' --exclude='*'. Otherwise, maybe
you want a second -F?
On 3/6/23 16:04, Heiko Schlittermann via rsync wrote:
Oh, yeah, I missed that part. Yeah, don't do that; it's easy to add
a lock file to a shell script.
On Sun, Mar 05, 2023 at 12:30:16PM +0100, Hardy via rsync wrote:
> I second Francis here. You don't need to diagnose incomplete file transfers
> as long as you have racing conditions as you
I second Francis here. You don't need to diagnose incomplete file transfers as
long as you have racing conditions as you described. This leads to strange
result inevitably.
NEVER start several rsync jobs manipulating the same data - especially if there
are modifications to BOTH sides source
1 - 100 of 17085 matches
Mail list logo
