It's possible to have situation when current directory is not needed for
rsync operation (using absolute path on lazy mounts / being in deleted
directory).
rsync should not fail in such cases
---
util.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/util.c b/util.c
is recording timestamps incorrectly.
On Fri, Jun 23, 2023 at 12:57:02PM -0400, . via rsync wrote:
I'm using rsync to copy files from a source folder to a destination folder.
It works fine. But, to save some time, what options should I use to only
update or copy (to the destination) files that are new
I'm using rsync to copy files from a source folder to a destination
folder. It works fine. But, to save some time, what options should I
use to only update or copy (to the destination) files that are new
and/or have a new time stamp on them?
Here's the code I use below (pretty sure the -n
a case of a
file with matching mtime+size but not matching checksum due to gzip's
metadata even though the uncompressed result is identical. I would not
consider this to be a case worth updating the remote copy but I am sure
someone will disagree.
On 03/23/2017 03:49 PM, Kevin Korb via rsync
, steven banville via rsync wrote:
>
> Hi
>
>
> I am using "rsync" to send files from a source machine to a remote
> machine as one typically does. I would like to clarify that the "-c"
> option will cause the checksum on the receiving end to be crea
Hi
I am using "rsync" to send files from a source machine to a remote machine as
one typically does. I would like to clarify that the "-c" option will cause
the checksum on the receiving end to be created by reading the already written
file and NOT the data stream on the receiving end.
samba-b...@samba.org wrote:
--snipp--
It seems that pv is waiting for data from rsync, and rsync is waiting for data
too (stuck in select()) and not closing the input to pv. So it's a deadlock.
Same happens when you substitute pv with something else (like dd). It seems
that those commands just
Brian,
On 2017-03-21 07:35, Brian K. White via rsync wrote:
Any possibility of a version of rsync that doesn't need RSH or SSH?
rsync already doesn't need rsh or ssh.
* On host A (server, with room to accept big uploads):
Edit /etc/rsyncd.conf, add this to the end:
[hostb]
path
Hello,
While restoring a large data backup which contained some big sparse-ish files,
using rsync 3.1.1, (these were VMDK files to be precise), I found that adding
the --sparse option can permanently wedge the rsync processes.
I performed a few basic checks during the time it happened (at one
Dear All,
Along with the files that suddenly disappear, we have a bit of a problem
with these that do not.
Namely, in my test runs I can see a small but stable set of files, that
rsync is repeatedly trying to transfer, and then repeatedly fails to
updates their times ; and then the story
Sorry to keep replying to myself:
> Because this is a Time Machine backup, and there were 66 snapshots of a
> 1 TB disk consuming about 1.5 TB, there were a *lot* of hard links. Many
> of directories rather than individual files, so it's a little
Err, whoops? No, I was tired and confused. They
> But at first blush, it appeared that adding - made things hang
> forever.
Yes. Confirmed against the git HEAD (9e7b8ab7cf66ecd152002926a7da61d8ad862522).
Running:
rsync -n -iaHJAX $d $b
Does some initial work and then gets to:
bash-3.2# lldb -p 6458
(lldb) process attach
There are huge differences between source files in the version 3.0.9
released as a tar.gz and source files in git. I would assume that the
released version would correspond to the version in git but with 3.0.9
it is not like that. In 3.1.0 the released and git versions are more or
less the same.
Dear All,
We sometimes have to replicate large "live" filesystems with many (
sometimes millions, up to few hundred millions ) files on them. (
Copying actively used files is of course a bad idea, but it really helps
to keep the delta small, so one final transfer can later save the day. )
Fedorov via rsync wrote:
> Dear All,
>
> We sometimes have to replicate large "live" filesystems with many (
> sometimes millions, up to few hundred millions ) files on them. (
> Copying actively used files is of course a bad idea, but it really helps
> to keep the delta
Am 05.04.2017 um 22:05 schrieb L A Walsh via rsync:
>I ran rsync 3.1.1 for over a year to help generate
> snapshots. I can't say if it copied all the files or not, as
> it was backing up a large "/home" partition, BUT, it never hung.
> It did take 45min to a few h
just subscribed for rsync-qa from bugzilla via rsync wrote:
Hard link handling seems to be broken when using "rsync -aH --compare-dest". I
found two possible scenarios:
1) rsync completes without error message and exit code 0, although some files
are missing from the backup
2) rs
I am using rsync on an unreliable mobile WAN connection, which causes rsync
receiver to hang for long time, when connection is broken during transfere. As
the option "--timeout=" here does not hit for me, is there a recommended "best"
method to detect such scenario ? --
Please use reply-all
I am using rsync on an unreliable mobile WAN connection, which causes rsync
receiver to hang for long time, when connection is broken during transfere.
As the option "--timeout=" here does not hit for me, is there a recommended
"best" method to detect such scenario ?--
Please use reply-all for
Le 2017-04-07 21:08, Kevin a écrit :
On 04/07/2017 03:07 PM, McDowell, Blake wrote:
I run --times when I use rsync […] but the times do not transfer over
[…]
I have never seen rsync do that. What exactly are you doing?
I have seen such a behaviour when trying to rsync to a UDF volume
Hi:
I'm in the middle of recoverying from a tactical error copying
around an Mac OS X 10.10.5 Time Machine backup (turns out Apple's
instructions aren't great...), and I had rsync running for the past 6
hours repairing permissions/acls on 1.5 TB of data (not copying the
data), and then it
> I guess I can turn on core dumps and increase (unlimit completely) the
> stack size...
>
> Although it doesn't seem to have segfaulted, so I'm not sure having
> core dumps enabled would have helped?
Indeed. I reran it on the 50 remaining individual directories,
it seems to have made it
In Linux I would handle this with a pvmove. I don't know how to make it
happen in Windows other than using a disk image.
BTW, you will probably find -i to be much more useful than a second (or
even a first) -v
On 04/12/2017 07:31 PM, Rene J Suarez-Soto via rsync wrote:
> I am running rs
+03:00 <devz...@web.de>:
> What's the value of "i" when this happens and what are the system ulimit
> values for the user running that?
>
> Roland
>
>
>
>> Gesendet: Freitag, 14. April 2017 um 19:22 Uhr
>> Von: "Boris Savelev via rsync"
What's the value of "i" when this happens and what are the system ulimit values
for the user running that?
Roland
> Gesendet: Freitag, 14. April 2017 um 19:22 Uhr
> Von: "Boris Savelev via rsync" <rsync@lists.samba.org>
> An: rsync@lists.samba.org
> B
People,
This doesn't seem possible - would it be possible to hack a version of
rsync to do it?
As an exercise, I want to create a VM image (or at least backup of all
the files with rsync) from a SCSI drive in an old Red Hat (NOT
Enterprise) v5.2 Linux 486 machine (circa 1999 that does have
Kevin,
I know a KK - I have talked to him about Sydney Futurists stuff and
politics etc . . different email address though . .
See inline comments:
On 2017-03-14 16:17, Kevin Korb via rsync wrote:
Rsh should be pretty easy to do. I don't think it has changed since
before RH5.2 vintage
Hi,
We're encountering a rather weird, sporadic hang during a large-file
transfer. A bit of background on the setup:
- Host A rsyncs a MySQL database from Host B. Both sides use rsync
3.1.1 on Debian Jessie.
- Host B serves the files using rsync --daemon from an ext4 filesystem
to . paths it would be:
rsync -aHvv --compare-dest=../dstlt/. srclt/. baklt/.
Also, all these params that end with /. the . is kinda pointless despite
being points ;)
On 04/05/2017 07:19 PM, L A Walsh via rsync wrote:
> just subscribed for rsync-qa from bugzilla via rsync wrote:
>> Proba
How do I transfer just the modification times with rsync? I now the file
content is the same but the modification times are different. Is there a way to
do this? Every way that I have tried causes the whole file to transfer as well.
Thanks
--
Please use reply-all for most replies to avoid
know why...
B
From: rsync [rsync-boun...@lists.samba.org] on behalf of Kevin Korb via rsync
[rsync@lists.samba.org]
Sent: Friday, April 07, 2017 2:58 PM
To: rsync@lists.samba.org
Subject: Re: modification times questions
If you are sure the content
f times. When I run rsync a second time with
> your suggestion the times do transfer over. I don't know why...
>
> B
>
> From: rsync [rsync-boun...@lists.samba.org] on behalf of Kevin Korb via rsync
> [rsync@lists.samba.org]
>
hierachical filter rule list on stdin.
PS: Yes to simply ignore code 24 would be correct. However, it creates exit
code 2 in these cases.
On Fri, Apr 7, 2017 at 2:58 PM, Georgy Fedorov via rsync <
rsync@lists.samba.org> wrote:
> Dear All,
>
> We sometimes have to replic
If you are sure the content is correct you can run rsync with both
--times and --size-only.
This will cause rsync to "fix" the timestamps on files that are the same
size on both ends.
On 04/07/2017 02:53 PM, McDowell, Blake via rsync wrote:
> How do I transfer just the modif
I guess I should also mention that if both trees are local you can use:
find . -print -exec touch "/path/to/wrong/times/{}" --reference "{}" \;
On 04/07/2017 02:58 PM, Kevin Korb via rsync wrote:
> If you are sure the content is correct you can run rsync with both
&g
gt; to transfer the files because of times. When I run rsync a second time with
> your suggestion the times do transfer over. I don't know why...
>
> B
>
> From: rsync [rsync-boun...@lists.samba.org] on behalf of Kevin Korb via rsync
&g
Exit code 2 is "Protocol incompatibility".
Also, sounds like what you really want is --files-from
On 04/07/2017 10:01 AM, Axel Kittenberger via rsync wrote:
> With this two options on a very live system you may need to take into
> account this bug as well I reported a while
>
> Also, sounds like what you really want is --files-from
>
files-from is part of the command.
--
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:
chical filter rule list on stdin.
PS: Yes to simply ignore code 24 would be correct. However, it creates
exit code 2 in these cases.
On Fri, Apr 7, 2017 at 2:58 PM, Georgy Fedorov via rsync
<rsync@lists.samba.org <mailto:rsync@lists.samba.org>> wrote:
Dear All,
We sometimes
Hello!
I use rsync from python on my Debian Jessie amd64 and get this error:
*** buffer overflow detected ***: /rsync terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x731af)[0x778971af]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7791caa7]
Doing some research, I see there’s an outstanding patch for Sami Farin’s
fsync() feature:
https://git.samba.org/?p=rsync-patches.git;a=blob_plain;f=fsync.diff;hb=HEAD
Is there any intention to migrate this patch into master?
— Jim
--
Please use reply-all for most replies to avoid omitting the
I don't get why it runs from the command line but not from a scheduled task.
Any suggestions for a fix or a work-around?
--
View this message in context:
Hello, all. I've encountered an odd error that I haven't been able to
identify and resolve myself. Hoping someone here could provide some
guidance.
I'm using the following command to rsync files between two servers, over
the internet (if that matters), via SSH:
rsync -ahu --timeout=600
Dear experts,
I would like get your help for the issue with --partial-dir=*absolute path.*
I’m trying to use rsync to send big file to server and config
--partial-dir=*absolute
path* since I want to store temp partial file in /tmp/ directory and keep
the destination folder clear.
My
You should use rrsync for that.
On 08/15/2017 08:58 PM, Jared via rsync wrote:
> Hi, Kevin. Thank you for the suggestion. It triggered a memory that I
> had set some restrictions on this rsync copy a while back. Sure enough,
> in ~/.ssh/authorized_keys:
>
> command=
With rsyncd you can't. You would have to switch to rsync over ssh...
rsync -a --delete --delay-updates --partial-dir=/tmp -P /home/joe/rsync/
10.148.34.28:/home/joe/rsync/
Also, when you use --partial-dir you probably want to also use --temp-dir.
On 08/15/2017 07:19 PM, Joe Qiao via rsync
Have you tried doing the clean shell test?
ssh -i /path/to/key u...@remote.server.com true > testfile
if testfile isn't 0 bytes then whatever is producing the data that ended
up in there is your problem.
On 08/15/2017 04:13 PM, jared via rsync wrote:
> Hello, all. I've encountered an odd
M0vBC
drwx-- 2 lightdm lightdm 4096 Aug 7 09:24 pulse-PKdhtXMmr18n
-rw-rw-r-- 1 lightdm lightdm 0 Aug 7 09:24 unity_support_test.1
-r--r--r-- 1 rootroot 11 Aug 7 09:23 .X0-lock
drwxrwxrwt 2 rootroot 4096 Aug 7 09:23 .X11-unix
Anyway, at least the
n --delete in the appropriate spot fixed the issue.
That's a big whoops on my part. :-) Appreciate the pointer.
--
Jared
On 08/15/2017 07:20 PM, Kevin Korb via rsync wrote:
> Have you tried doing the clean shell test?
>
> ssh -i /path/to/key u...@remote.server.com true > testfile
>
Hi
I am having a problem with rsync freezing and I would like to collect the
proper information while the problem happens. However, I would like to ask some
clarifications.
rsync-debug
===
I see references of using rsync-debug but I cannot figure out how to use it
*while* the rsync
Please add the following to the rsync-related documents list on
https://rsync.samba.org/resources.html
https://sites.google.com/site/rsync2u/home
rsync2u is a job-driven bash script that uses rsync to backup files to a local
USB device or disk. You write the job & exclude files and rsync2u
On https://rsync.samba.org/lists.html page, the archive 2 link is broken.
Wolfram Volpi--
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:
rsync --delete option tells rsync to delete extraneous files from the receiving
side (ones that aren't on the sending side).But if a user accidentally deletes
a file, there is no way to restore it from the server.If --delete option is not
used, and the local hard disk is destroyed, restored
--backup-dir. Each file that would be replaced or deleted is
instead moved into the backup directory. The backup directory can be
time stamped to make pruning easier.
On 07/25/2017 12:56 PM, Wolfram Volpi via rsync wrote:
> rsync --delete option tells rsync to delete extraneous files f
.
On 07/02/2017 03:23 PM, Peter via rsync wrote:
> Dear developers,
>
> In the rsync's manpage, there is a line describing the "archive mode"
> option:
>
> -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)
>
> Archive mode means that all data is
Dear developers,
In the rsync's manpage, there is a line describing the "archive mode"
option:
-a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)
Archive mode means that all data is backed up sensibly while the same
doesn't apply for all metadata (hence the mentioned -H, -A
Setting up a new system backup (done several before and they all work fine).
Windows 10 x64 (cygwin with rsync version 3.1.2) backing up to ubuntu
server 16.04 (rsync 3.1.1). Run test.bat from command window (run as
administrator) and it runs fine.Created scheduled task that runs test.bat
and
leonv12 via rsync <rsync@lists.samba.org> wrote:
> I don't get why it runs from the command line but not from a scheduled
> task. Any suggestions for a fix or a work-around?
Check the environment settings, which are often the cause of differences
in behavior between running from
Hi,
Currently I'm developing an rsync packet sniffer and I'm trying to understand
the basics of the network protocol.
I had a hard time analyzing the source code and couldn't find the answers to
the 2 main issues I have:
1. How do I detect the end of the file list message(s) sent by the
Hi
I rsync from 4 machines to a single destination one, and I am certain the
filenames they sync do not overlap. But from time to time rsync from a source
machine gets stuck (not always the same source machine).
I followed https://rsync.samba.org/issues.html and I gathered strace, lsof and
Hi folks,
I have to migrate a set of iscsi backstores to a new target via network.
To reduce downtime I would like to mirror the active volumes first, next
stop the initators, and then do a final incremental sync.
The backstores have a size between 256 GByte and 1 TByte each. In toto
its about 8
You can also look at chunksync http://chunksync.florz.de/
Marian
On 06/26/2017 09:27 PM, Harald Dunkel via rsync wrote:
> Hi folks,
>
> I have to migrate a set of iscsi backstores to a new target via network.
> To reduce downtime I would like to mirror the active volumes first,
Calling chmod only on (optimization: non-empty) directories would fix this.
I don't need to chmod a *file* before unlinking it,
I just need write permission on the directory it is located in.
(Now you have to convince the "appliance" to use a patched rsync ...)
Cheers,
Lars Ellenberg
Does rsync -aAXv /dir1 /dir2, where dir2 is a mounted FAT formatted SD
card, and then:
rsync -aAXv /dir2 /dir1, to restore the files in dir1 from the FAT
formatted SD card, restore the ACL and owner/permissions of the files
and directories in dir1?
Thanks,
John
--
John Conover,
changes your clock (assuming it does).
Unless you have FAT on both ends you probably don't want FAT at all.
On 05/16/2017 04:30 PM, John Conover via rsync wrote:
>
> Does rsync -aAXv /dir1 /dir2, where dir2 is a mounted FAT formatted SD
> card, and then:
>
> rsync -aAXv /dir2 /d
On Thu, Jun 08, 2017 at 07:09:24AM +, just subscribed for rsync-qa from
bugzilla via rsync wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=12806
>
> --- Comment #4 from Heinz-Willi Wyes <h...@delember-wyes.de> ---
> I got a personal message from Lars Ellenberg that went
How exactly does rsync determine that the copy has the incorrect
timestamp and not the source file?
Does it assume that the copy must be incorrect or are there other
criteria that have to be considered?
Quoting Kevin Korb via rsync <rsync@lists.samba.org>:
Whenever you use -
At 08:11 12.06.2017, max.power--- via rsync wrote:
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>
>How exactly does rsync determine that the copy has the incorrect
>timestamp and not the source file?
>Does it assume that the copy must be incorrect or are there
On Mon 12 Jun 2017, max.power--- via rsync wrote:
> How exactly does rsync determine that the copy has the incorrect timestamp
> and not the source file?
The source by definition is correct.
Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsub
When a file of same length already exists at the destination then the
command 'rsync --archive --size-only' (--archive is same as -rlptgoD)
may change the modification time of the destination file even if no
modification was made.
Type the following commands in a terminal in order to
a is known to have not changed.
These options allow rsync to correct the incorrect timestamps without
even looking inside of the files. If you are not 100% sure your file
data matches you should not be using --size-only.
On 06/11/2017 09:28 AM, max.power--- via rsync wrote:
> When a file o
Ok, that clears things up.
Thanks.
Quoting Paul Slootman via rsync <rsync@lists.samba.org>:
On Mon 12 Jun 2017, max.power--- via rsync wrote:
How exactly does rsync determine that the copy has the incorrect timestamp
and not the source file?
The source by definition is correct.
> On 15 Jun 2017, at 19:29, Karl O. Pinc via rsync <rsync@lists.samba.org>
> wrote:
>
> On Thu, 15 Jun 2017 13:23:44 +
> just subscribed for rsync-qa from bugzilla via rsync
> <rsync@lists.samba.org> wrote:
>
>> https://bugzilla.samba.org/show_bug.
--delete means delete from the target what isn't on the source (except
what is excluded). Those look like temp files. Possibly from another
rsync that is running at the same time.
On 05/01/2017 12:36 AM, Chandana De Silva via rsync wrote:
> All,
> I have an rsync based backup process whic
On Fri, Apr 14, 2017 at 10:22 AM, Boris Savelev via rsync <
rsync@lists.samba.org> wrote:
> #8 0x55585ef6 in read_int (f=f@entry=1606) at io.c:1711
>
#9 0x555876ed in setup_protocol (f_out=1605, f_in=1606) at
> compat.c:158
>
Since rsync is just trying to
:
> On Tue, Apr 04, 2017 at 11:12:11AM +0200, Michal Ruprich via rsync wrote:
>> There are huge differences between source files in the version 3.0.9
>> released as a tar.gz and source files in git. I would assume that the
>> released version would correspond to the version
On Fri, Apr 14, 2017 at 08:22:29PM +0300, Boris Savelev via rsync wrote:
> I use rsync from python on my Debian Jessie amd64 and get this error:
> *** buffer overflow detected ***: /rsync terminated
> I rebuild rsync-3.1.1 from Debian source with debug and -O1 and get bt from
> gdb
se contact the sender by reply email and destroy all copies of
the original message.
From: rsync [rsync-boun...@lists.samba.org] on behalf of Kevin Korb via rsync
[rsync@lists.samba.org]
Sent: Thursday, March 23, 2017 1:10 PM
To: rsync@lists.samba.org
S
original message.
>
> ____
> From: rsync [rsync-boun...@lists.samba.org] on behalf of Kevin Korb via rsync
> [rsync@lists.samba.org]
> Sent: Thursday, March 23, 2017 1:10 PM
> To: rsync@lists.samba.org
> Subject: Re: rsync: "-c" opt
Hi
I am seeing from time to time the following error:
rsync: rename "/DEST_DIR/SUB_DIR/.A_FILE.AzmlvG" ->
"SUB_DIR/.tmp/A_FILE.xml.gz": No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1183)
I rsync from a few source
Greetings rsync gurus,
As I understand the documentation "--backup" without specifying "--backup-dir"
implicitly sets "--omit-dir-times".
It is then possible to negate the implied option by specifying it prefixed with
"--no".
The resulting option "--no-omit-dir-times" runs without any warnings
On Sat, Sep 16, 2017 at 10:13 AM, Anders Gronberg via rsync <
rsync@lists.samba.org> wrote:
> As I understand the documentation "--backup" without specifying
> "--backup-dir" implicitly sets "--omit-dir-times".
> It is then possible to negate
On Wed, Sep 6, 2017 at 1:00 AM, Pavel Kasparek via rsync <
rsync@lists.samba.org> wrote:
> when the "write only = yes" option is used on rsync server, [... would a]
> hacked client [...] be able to get the list of remote dir [?]
It wouldn't work. The listing action is
> On 06 Oct 2017, at 12:24, Frank Steiner via rsync <rsync@lists.samba.org>
> wrote:
>
> Hi,
>
> I just stepped on a strange and very annoying bug in rsync-3.1.0 as
> shipped with SuSE Linux Enterprise 12, but verified the bug also
> with rsync-HEAD-20170123.
&
Hi,
I just stepped on a strange and very annoying bug in rsync-3.1.0 as
shipped with SuSE Linux Enterprise 12, but verified the bug also
with rsync-HEAD-20170123.
I tried to copy some of my movie collection to a usb disk that our
TV could read, so it was formatted with vfat. I forgot that vfat
On 10/08/2017 06:19 PM, Wayne Davison wrote:
> On Wed, Sep 6, 2017 at 1:00 AM, Pavel Kasparek via rsync
> <rsync@lists.samba.org <mailto:rsync@lists.samba.org>> wrote:
>
> when the "write only = yes" option is used on rsync server, [...
> would
Hi all,
I'm a bit confused about the log-file option for the daemon rsync.
What the rsyncd.conf manual page says about the 'log file' option in
rsyncd.conf:
"This setting can be overridden by using the --log-file=FILE or
--dparam=logfile=FILE command-line options. The former overrides all
the
Subject: Re: Is it possible to transfer a large, dynamic file in a piecemeal
fashion? Yes it is.
Don Kuenz via rsync <rsync@lists.samba.org> wrote:
> Greetings,
>
> Is it possible to use rsync to transmit a large, dynamic 2TB file in a
> piecemeal fashion during daylight hou
Kevin Korb via rsync <rsync@lists.samba.org> wrote:
> [-- multipart/signed, encoding 7bit, 98 lines --]
>
>[-- multipart/mixed, encoding 7bit, 72 lines --]
>
>[-- text/plain, encoding quoted-printable, charset: utf-8, 65 lines --]
>
> You probably want --i
You probably want --inplace for this rather than partial. The upside of
--partial is that the existing file isn't replaced until there is a
complete file to replace it with. The downside is building up that
entire new file.
On 09/05/2017 12:01 AM, Don Kuenz via rsync wrote:
> Subject:
Hello all,
when the "write only = yes" option is used on rsync server, the client
can't download any file from the server.
My question is, if in that case the rsync protocol will allow the client
to read the server directory content or not. The question is not about
if standard rsync client will
On Tue 05 Sep 2017, Vangelis Katsikaros via rsync wrote:
> On 08/30/2017 05:39 PM, Paul Slootman wrote:
> > On Wed 23 Aug 2017, Vangelis Katsikaros via rsync wrote:
> >
> >> abc 3797 3796 0 01:12 ?00:03:14 /usr/bin/rsync --compress
> >>
On 08/30/2017 05:39 PM, Paul Slootman wrote:
> On Wed 23 Aug 2017, Vangelis Katsikaros via rsync wrote:
>
>> abc 3797 3796 0 01:12 ?00:03:14 /usr/bin/rsync --compress
>> --compress-level=9 --bwlimit=512k --recursive --delay-updates --quiet
>> --update
Hi
I would like to ask, when the "vanished files" warning is a sign that something
bad is happening somewhere. I know that the `rsync-no-vanished` script can
silence the warning, but I am wondering whether this is a sane thing to do.
My guess based on
All it means is that rsync saw a file that needed transferring but the
file was gone when rsync actually tried to open it. So look at the
filenames and decide if it is a problem or not.
On 09/07/2017 10:27 AM, Vangelis Katsikaros via rsync wrote:
> Hi
>
> I would like to ask, when the
Hi Kevin
Thanks for the tip. In my case it seems it's fine!
Regards
Vangelis
On 09/07/2017 08:51 PM, Kevin Korb via rsync wrote:
> All it means is that rsync saw a file that needed transferring but the
> file was gone when rsync actually tried to open it. So look at the
> filenames a
--list-only (or no target specified) are the only listings without
transferring that rsync supports. The restriction would not apply to
the list of modules (IIRC there is another option for that).
On 09/06/2017 04:00 AM, Pavel Kasparek via rsync wrote:
> Hello all,
>
> when the &q
Greetings,
Is it possible to use rsync to transmit a large, dynamic 2TB file in a
piecemeal fashion during daylight hours over the course of a dozen days?
On a good day, about 200GB of data can be transferred before rsync times
out to enable a nightly local backup to complete. The local backup
Hello all,
I reported an integer overflow issue in the bugzilla (
https://bugzilla.samba.org/show_bug.cgi?id=12568), but I haven't received
any response so far.
I was wondering could you please take a look at this report and give me
some feedback.
Thanks and look forward to your reply.
--
On Tue 15 Aug 2017, Joe Qiao via rsync wrote:
> Thanks so much for the quick reply, Kevin!
>
> I tried with ssh and --partial-dir, it looks the partial file still will be
> stored in local dir, but not in /tmp.
>
>
> Every 1.0s: ls -al /home/joe/rsync/ /tmp/
>
1 - 100 of 1983 matches
Mail list logo
