On Thu, Nov 17, 2011 at 3:08 AM, Axel Kittenberger axk...@gmail.com wrote:
I never figured out how I should tread error 13 from rsync, Problem with
diagnostics. My question is, is this a transient or permanent error?
Rsync mainly outputs it when trying to log information, so it would
I never figured out how I should tread error 13 from rsync, Problem
with diagnostics. My question is, is this a transient or permanent
error? Or how seriously did something go wrong when rsync returns 13?
I don't get much smarter reading the rsync source either.
For reference this is for Lsyncd
Hello,
Is your output on this problematic network similar to the following :
$ telnet mirrors.usc.edu 873
Trying 68.181.195.4...
Connected to hpc-mirror.usc.edu.
Escape character is '^]'.
@RSYNCD: 30.0
Also, what happens if you add -n (--dry-run) to the following command :
rsync -artv
Thanks for the response..
Is your output on this problematic network similar to the following :
$ telnet mirrors.usc.edu 873
Trying 68.181.195.4...
Connected to hpc-mirror.usc.edu.
Escape character is '^]'.
@RSYNCD: 30.0
Yes, this is exactly the output.
Also, what happens if you add -n
Hello,
It seems that the issue is todo with the network. However, I would suggest you
try with a different computer system to be sure. Additional notes follow :
--
server: iperf -s -D -p 873
(problematic network) client: iperf -c iperf.server.com -L 873
-logDtpre.is .
centos/5.6/updates/i386/RPMS/
rsync: read error: Connection reset by peer (104)
_exit_cleanup(code=12, file=io.c, line=759): entered
rsync error: error in rsync protocol data stream (code 12) at io.c(759)
[receiver=3.0.6]
_exit_cleanup(code=12, file=io.c, line=759): about to call exit(12
from Wayne Davison way...@samba.org 2011-09-22 16:51:55 UTC ---
If a filename contains a 0x5C (/) character, then that character will be
treated as a path delimiter. The error you're seeing looks to be causued by
the missing directories in what is taken to be a pathname (though rsync doesn't
know
https://bugzilla.samba.org/show_bug.cgi?id=8471
--- Comment #3 from Wayne Davison way...@samba.org 2011-09-22 16:59:01 UTC ---
Sorry, I should have double-checked your hex vs char statement. Slash is 0x2F
(/), whereas backslash is 0x5C (\). I'm not sure why the presence of a
backslash would
=UTF-8 is included, same error happens.
So pls close this problem file as latest Rsync does not have any problem
against latest version of destination file system.
Again thank you for taking your time.
Takeshi Sakai
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
https://bugzilla.samba.org/show_bug.cgi?id=8471
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://bugzilla.samba.org/show_bug.cgi?id=8471
Summary: The file of DBCS file name contains DBCS second byte
of x'5C' cause error.
Product: rsync
Version: 3.0.8
Platform: All
OS/Version: All
Status: NEW
), with this NAS, even the file copying by windows
command also causes file not found error, where the file is used same with
rsync operation. Then I began the investigation with latest rsync and samba.
I give up for older version correction, though would like to fix on latest
version.
That's all my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Local rsync version 3.0.7 protocol version 30.
The remote rsync version is 3.0.5, I think.
opensuse v11.3
linux 2.6.34.8-0.2-desktop x86_64
The nightly rsync run is getting this error:
2011/07/20 02:04:29 [17840] FATAL I/O ERROR
In 4e27066a.4080...@sohnen-moe.com, on 07/20/11
at 09:46 AM, James Moe ji...@sohnen-moe.com said:
The nightly rsync run is getting this error:
2011/07/20 02:04:29 [17840] FATAL I/O ERROR: dying to avoid a \
--delete-during issue with a pre-3.0.7 receiver
The options are:
- --archive
Version|3.0.7 |3.0.9
Resolution||FIXED
--- Comment #3 from Wayne Davison way...@samba.org 2011-06-18 19:52:43 UTC ---
Errors will be more error-like in 3.0.9.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You
On Sun, May 29, 2011 at 11:04:25PM -0700, travis+ml-rs...@subspacefield.org
wrote:
Could a dangling symlink cause this problem?
To answer my own question, yes, a dangling symlink on the source was
the cause of the problem, and I had --copy-unsafe-symlinks is on.
Thanks for the help people,
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #5 from Dal dtama...@bloomberg.net 2011-06-01 07:58:01 UTC ---
The issue happens intermittently. Most of the time large files are sync'd fine.
I have run rsync on the failed file several times now and it hasn't failed. Is
there any
On Wed, Apr 06, 2011 at 11:44:45AM +0200, Paul Slootman wrote:
On Tue 05 Apr 2011, travis+ml-rs...@subspacefield.org wrote:
Anyone know what this is supposed to mean?
366305 files to consider
IO error encountered -- skipping file deletion
I keep getting this, and so it refuses
https://bugzilla.samba.org/show_bug.cgi?id=8090
--- Comment #2 from Wayne Davison way...@samba.org 2011-05-30 17:29:11 UTC ---
full_fname() is calling asprintf(). Perhaps that is not supported on Solaris
5.8? You could try using the version supplied by lib/snprintf.c (e.g.
manipulating the
https://bugzilla.samba.org/show_bug.cgi?id=6183
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|NEEDINFO
--- Comment #4
},{60.00 }) = 1
(0x1)
44755: 4552.250720436 0.000172936 read(4,0x2832d94c,1712) = 1 (0x1)
44179: 5266.607031995 0.70125
write(4,\M-0\M-h\^DH\M-U\M-%i\M-v\M-{\M-UQ\M-\\^U\M-J\^C\^\Y|\M-~\^U\^E...,1911)
ERR#54 'Connection reset by peer'
44755: 4552.251465543 0.000424099 write(2,rsync: read error
https://bugzilla.samba.org/show_bug.cgi?id=8090
Summary: full_fname out of memory error on missing file SunOS
5.8
Product: rsync
Version: 3.0.7
Platform: Sparc
OS/Version: SunOS
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=8090
--- Comment #1 from Jason Martin jm9...@att.com 2011-04-15 20:11:15 UTC ---
Created attachment 6409
-- https://bugzilla.samba.org/attachment.cgi?id=6409
truss output of problem.
--
Configure bugmail:
On Tue 05 Apr 2011, travis+ml-rs...@subspacefield.org wrote:
Anyone know what this is supposed to mean?
366305 files to consider
IO error encountered -- skipping file deletion
I keep getting this, and so it refuses to delete any files from a mirror.
But what is the supposed I/O error
On Tue, Apr 5, 2011 at 4:18 PM, travis+ml-rs...@subspacefield.org wrote:
366305 files to consider
IO error encountered -- skipping file deletion
Is that to an rsync daemon? If so, check the daemon's log for an
error. The daemon may have decided to just log the error and not send
Anyone know what this is supposed to mean?
366305 files to consider
IO error encountered -- skipping file deletion
I keep getting this, and so it refuses to delete any files from a mirror.
But what is the supposed I/O error?
Can we have it give us some kind of clue?
dmesg doesn't show any
https://bugzilla.samba.org/show_bug.cgi?id=7981
--- Comment #1 from marcin.cies...@gmail.com 2011-03-02 10:05 CST ---
Created an attachment (id=6275)
-- (https://bugzilla.samba.org/attachment.cgi?id=6275action=view)
trivial fix
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=7981
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
fw.school158.gp-online.net (41.161.29.109)
Mar 1 11:23:14 rsynchead1 rsyncd[18773]: rsync: connection unexpectedly closed
(24 bytes received so far) [Receiver]
Mar 1 11:23:14 rsynchead1 rsyncd[18773]: rsync error: error in rsync protocol
data stream (code 12) at io.c(601) [Receiver=3.0.7]
What I
https://bugzilla.samba.org/show_bug.cgi?id=7975
m...@mattmccutchen.net changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7956
Summary: Don't error when attempting to delete a non-existent
default ACL
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=7956
--- Comment #1 from ch...@onthe.net.au 2011-02-14 20:23 CST ---
Created an attachment (id=6247)
-- (https://bugzilla.samba.org/attachment.cgi?id=6247action=view)
Patch to fix deleting non-existent default ACL
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=7956
--- Comment #2 from m...@mattmccutchen.net 2011-02-14 20:34 CST ---
How can the situation arise? If it arises only by a concurrent modification to
the destination, I don't care much. There are lots of ways rsync can mess up
with
||INVALID
--- Comment #3 from ch...@onthe.net.au 2011-02-14 21:14 CST ---
I was seeing the error on an rsync -A into a fresh destination, where the
destination directory itself doesn't have a default ACL.
...doh! As it turns out, the error was because my destination
If pushing data (e.g. a local copy or copy from local to remote), there is a
failure where the receiver can try to report an error, die, and the sender
gets the error trying to write to the receiver before it gets the error
message from around the horn (it would have gone to the generator
If pushing data (e.g. a local copy or copy from local to remote), there is a
failure where the receiver can try to report an error, die, and the sender
gets the error trying to write to the receiver before it gets the error
message from around the horn (it would have gone to the generator
Begin forwarded message:
From: Mike Bombich m...@bombich.com
Date: March 10, 2009 11:17:36 PM CDT
To: rsync@lists.samba.org
Subject: rsyserr is occasionally dropping receiver messages
Typically rsync exits and reports an error such as:
rsync: writefd_unbuffered failed to write 4 bytes
has experienced an out of disk space error and not had a message similar
to the following reported :
rsync: mkstemp
/Volumes/backup_volume/backups/Section.inprogress/to_backup/file_for_which_there_is_not_enough_space.n3pq0e
failed: No space left on device (28)
rsync_v3.0.7(33235) malloc
I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike
Bombich's instructions at http://www.bombich.com/rsync.html. Rsync
repeatedly exits with a protocol data stream error when trying to copy
some com.apple.FinderInfo extended attributes. While testing this issue,
I found
From: Henri Shustak henri.shus...@gmail.com
Date: Thu, 3 Feb 2011 00:48:02 +1300
To: rsync rsync@lists.samba.org
Subject: Re: Protocol stream error on extended attribute, silent failure to
copy all attributes
[snip]
Recently, a user posted the following rsync error to the LBackup mailing
Hi,
My cron backup scripts often send me mails because of error 24 (Partial
transfer due to vanished source files). However, this is normal when backing up
user homes with IMAP folders. So I would like to suppress only this particular
error.
I have not found an rsync option to suppress
On Mon, Jan 31, 2011 at 01:35:20PM +0100, Mi wrote:
My cron backup scripts often send me mails because of error 24 (Partial
transfer due to vanished source files). However, this is normal when
backing up user homes with IMAP folders. So I would like to suppress only
this particular error
I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike
Bombich's instructions at http://www.bombich.com/rsync.html. Rsync
repeatedly exits with a protocol data stream error when trying to copy
some com.apple.FinderInfo extended attributes. While testing this issue,
I found that rsync
I'm using rsync 3.0.7 on Mac OS X 10.6, compiled with HFS+ enhancements
according to Mike Bombich's instructions at
http://www.bombich.com/rsync.html. Rsync repeatedly exits with a protocol
data stream error on some com.apple.FinderInfo extended attributes. While
testing this issue, I found
https://bugzilla.samba.org/show_bug.cgi?id=5458
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7807
--- Comment #1 from br...@aljex.com 2010-11-20 18:53 CST ---
The last two syntaxes are described in the man-page and of course they work.
The first syntax and anything else you invent will of course not work.
I see no bug.
--
https://bugzilla.samba.org/show_bug.cgi?id=7807
bugs.samba@hacking.co.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.samba.org/show_bug.cgi?id=7765
Summary: rsync error 23 without any real error
Product: rsync
Version: 3.0.7
Platform: PPC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=7765
--- Comment #2 from nvbolh...@aimvalley.nl 2010-10-29 08:40 CST ---
aha!
I tried many things to avoid the error, but forgot to try
the rsync option --exclude messages*
thanks for the quick response!
and btw. rsync is great (we used
I have had reports of problems with the -R option on OSX 10.6.4.
Just tested it myself and found this odd result:
When I run this
dtruss -f path/to/rsync -aHAXNR --fileflags --force-change
--protect-decmpfs --stats -v /Users/astrid/Documents/main.m
/Users/astrid/Desktop/rrr
it
(): Unknown error: 0 (0)
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1044) [sender=3.0.7]
PID/THRD SYSCALL(args) = return
609/0x11a0: sigaction(0x1E, 0xB5A0, 0x0) = 0 0
609/0x11a0: sigaction(0x1F, 0xB5A0
Hi again,
Problem solved
Sorry. I didn't even think to check permissions on the Desktop folder, the
first logical thing to check. Somehow they had been changed. Fixed them and -R
works fine now. I believe other users are likely having permissions issues too.
Thanks, Rob
--
Please use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
rsync v3.0.7 (also seen with 3.0.5)
linux 2.6.34-12-desktop x86_64
os/2 v4.50 fp3
rsync makes an unusual error when building its file list for a
transfer: it decided to move a directory further down the directory tree
than where it was located
https://bugzilla.samba.org/show_bug.cgi?id=4232
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On 15/08/10 14:06, Morgan Read wrote:
On 09/08/10 09:32, Matt McCutchen wrote:
On Sat, 2010-08-07 at 19:54 +1200, Morgan Read wrote:
I've been running this command, with the accompanying error:
[r...@mythtv ~]# ssh -t rs...@192.168.1.40 sudo rsync -avzAXH
--delete-after -e /home/rsync/bin
On 8/14/2010 3:09 AM, Matt McCutchen wrote:
On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote:
I have sample data that exposes this repeatably:
http://lists.samba.org/archive/rsync/2008-October/021889.html
Thanks, but we figured out the problem several months ago and it should
be fixed
On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote:
I have sample data that exposes this repeatably:
http://lists.samba.org/archive/rsync/2008-October/021889.html
Thanks, but we figured out the problem several months ago and it should
be fixed in rsync 3.0.7:
On 09/08/10 09:32, Matt McCutchen wrote:
On Sat, 2010-08-07 at 19:54 +1200, Morgan Read wrote:
I've been running this command, with the accompanying error:
[r...@mythtv ~]# ssh -t rs...@192.168.1.40 sudo rsync -avzAXH
--delete-after -e /home/rsync/bin/rsync_ssh /home/
building file list
, every time.
If I retry the exact same command but simply remove -z, or add -W, it
will work.
If I delete file.dat from the remote machine, sending new/file.dat will
also work normally with or without -z
The error happens before 10 megs of data have been sent, and the files
are each just over
On Sat, 2010-08-07 at 19:54 +1200, Morgan Read wrote:
I've been running this command, with the accompanying error:
[r...@mythtv ~]# ssh -t rs...@192.168.1.40 sudo rsync -avzAXH
--delete-after -e /home/rsync/bin/rsync_ssh /home/
building file list ... rsync: readlink_stat(/home/morgan/.gvfs
Hello List
I've been running this command, with the accompanying error:
[r...@mythtv ~]# ssh -t rs...@192.168.1.40 sudo rsync -avzAXH
--delete-after -e /home/rsync/bin/rsync_ssh /home/
r...@192.168.1.100:/mnt/bigdisk/morgansmachine/home
r...@192.168.1.100's password:
building file list ... rsync
readlink_stat(/home/morgan/.gvfs)
failed: Permission denied (13)
I believe the error above is a problem with the rsync user not being able to
read the file
/home/morgan/.gvfs. I suggest that you check the permissions on this file and
also check that the sudo command is in fact granting
script to finish.
Now the idea is simple, but I get an error.
When I let the post-xfer script of the queue share do the work in
stead of the pre-xfer script of the
backup share, everything works.
It looks as it isn't possible to run a seperate rsync command in the
pre-xfer phase.
Someone
On Wednesday 05 May 2010, Ryan Joseph wrote:
Hello again,
Moin,
I'm writing a compley backup application with rsync in shell.
What I do to report errors: analyze the return code an internal table with
error specifications and reporting these in clear text. The code:
# a list with all rsync
On May 5, 2010, at 10:41 PM, Michael Renner wrote:
I'm writing a compley backup application with rsync in shell.
What I do to report errors: analyze the return code an internal table with
error specifications and reporting these in clear text. The code:
You mean you just look
report errors like the one below but these make little
sense to people (including me) unless they are familiar with the internal
workings of rsync. It seems like there should be a more user friendly error
reporting that real users can understand instead of programmers lingo like
rsync
https://bugzilla.samba.org/show_bug.cgi?id=6405
--- Comment #3 from way...@samba.org 2010-04-24 15:38 CST ---
You have a superfluous colon after the port number.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because:
/test.bz2 rsync://automat...@localhost:1873:/automatiks
opening connection using: ssh rsync rsync --server -vve.s .
//automat...@localhost:1873:/automatiks
ssh: Could not resolve hostname rsync: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error
---
From: Henri Shustak henri.shus...@gmail.com
Date: Thu, 15 Apr 2010 15:39:11 +1200
To: rsync rsync@lists.samba.org
Subject: Re: Mac OS X rsync: unpack_smb_acl: sys_acl_get_info(): Unknown
error: 0 (0
I have also noticed this error. In my particular scenario ACL preservation is
not essential, but what concerns me is that rsync appears to skip an entire
folder that has an invalid ACL. Therefore none of the actual data is backed up.
I would expect rsync to copy the folder structure files
On Thu, 2010-04-15 at 00:21 +0100, Stuart Ramdeen (Toucan) wrote:
I have also noticed this error. In my particular scenario ACL
preservation is not essential, but what concerns me is that rsync
appears to skip an entire folder that has an invalid ACL. Therefore
none of the actual data
On Fri, 2010-04-09 at 11:12 +1200, Henri Shustak wrote:
An LBackup user recently posted a question to the mailing list asking about
the following error.
rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
Is it possible to place a feature request to have the error reported
An LBackup user recently posted a question to the mailing list asking about
the following error.
rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
Is it possible to place a feature request to have the error reported
by rsync also list the path to the problematic file
file_copy
You should see the following output quoted output provided you are running
rsync 3.0.7 :
rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1042) [sender=3.0.7]
What happens
I have further information regarding the version and the way rsync on these
systems was compiled. Installation and compilation was performed by using the
following instructions : http://www.bombich.com/mactips/rsync.html
I have reproduced this issue (no file path reported) with rsync 3.0.7.
I am a developer on the LBackup project.
An LBackup user recently posted a question to the mailing list asking about the
following error.
rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
Link to thread :
http://www.mail-archive.com/lbackup-discuss...@lists.connect.homeunix.com
the data, the following
error is reported :
rsync: mkstemp /path/to/somefile/file.pm.JKQczN failed: No such file
or directory (2)
If at all possible, I would like to use rsync v3 and make use of
various additional features. As I switch between versions I am
specifying the --rsync-path
The setup...
Transport is via SSH.
BoxA : Ubuntu 8.10
BoxB : Mac OS X 10.4.11
If I use rsync v2 to transfer data from BoxA to BoxB everything works fine.
However, if I use rsync v3 to transfer the data, the following error is
reported :
rsync: mkstemp
https://bugzilla.samba.org/show_bug.cgi?id=7124
Summary: Error exit causes I/O error
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
.
But when I try to backup /var/lib/zope2.9 I get an error 11. It does not
matter if zope is running or not.
[...]
get_local_name count=8387 /space/r5backup/boulder/1265202994//var/lib
_exit_cleanup(code=11, file=main.c, line=594): about to call exit(11)
It looks like you have captured only
On Fri, 2010-02-05 at 19:31 +0100, Michael Renner wrote:
I wrote a small backup script that use rsync: r5backup
(http://sourceforge.net/projects/r5backup/). It backup dozen of unix machines
for many people.
But when I try to backup /var/lib/zope2.9 I get an error 11. It does not
matter
Moin,
I wrote a small backup script that use rsync: r5backup
(http://sourceforge.net/projects/r5backup/). It backup dozen of unix machines
for many people.
But when I try to backup /var/lib/zope2.9 I get an error 11. It does not
matter if zope is running or not.
I can't see an error meassge
Hi,
based on a nightly cronjob we use rsync --delete to delete partitial
directory structure from a backup folder. Sometimes rsync is unable to
delete structure as told.
rsync: unlink /backup/usr/lib/gcc/x86_64-linux-gnu/4.1.3 failed: Is a
directory (21)
rsync error: some files/attrs were
Dear all!I'm using cwrsync (latest 4.0.3) which includes rsync 3.0.7 and Cygwin 1.7.1-1 to sync Win XP SP3 boxes with debian server (stable, rsync 3.0.3).On windows we have many Cyrillic file names. Debian box uses en_US.UFT-8.For some files I'm getting "file has vanished" error.
https://bugzilla.samba.org/show_bug.cgi?id=6719
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
/cron_rsyncexecute_prod.sh
building file list ... rsync error: received SIGUSR1 or SIGINT (code 20) at
rsync.c(231)
Rsync failure to rsync://omy2portalprodrs...@lnx09:9060/oMy2Lnx09Prod - Error
Code: 20. Error Desc: Received SIGUSR1 or SIGINT
Subject:Rsync failure to rsync://omy2portalprodrs...@lnx09:9060
Hello Rsync Support,
This is to give you more information.
Prior to the error below, I noticed in the logs that it keeps on
building file list. Then we tried to restart the rsync service at
10:25am. The service went working again at around 11:09:17am.
= Start of rsync Block @ Wed
Got this with
rsync --list-only --files-from=list directory dummy output 2 errors
to get a local file list:
...
rsync: link_stat file-name failed: No such file or directory (2)
rsync: link_stat file-name failed: No such file or directory (2)
rsync error: some files/attrs were not transferred
On Wed, Dec 23, 2009 at 7:25 AM, Carlos Carvalho car...@fisica.ufpr.brwrote:
Everything is normal except the last line. I don't understand the code
32 return value, I think it should be 23.
If you upgrade to a newer 3.1.0 you should find that bug was fixed a little
bit ago.
..wayne..
--
On Sun, Dec 13, 2009 at 8:47 PM, Matt McCutchen m...@mattmccutchen.net wrote:
But if the data block was exactly CHUNK_SIZE (32816), it would fill
the output buffer with nothing remaining, and the next call to inflate
would return Z_BUF_ERROR.
Thanks for tracking that down! I have fixed this
Hi Matt,
Thanks for your elaborate reply.
I am able to reproduce the error indeed running the suggested script:
inflate (token) returned -5
rsync error: error in rsync protocol data stream (code 12) at
token.c(476) [receiver=2.6.9]
rsync: connection unexpectedly closed (30 bytes received so far
the receiver encounters an error:
write(1, \34\0\0\10inflate (token) returned -5\n, 32) = 32
This is the compression error that has occasionally come up before:
http://lists.samba.org/archive/rsync/2004-December/09.html
http://lists.samba.org/archive/rsync/2006-May/015621.html
http
in pipe.c (routine
piped_child). Windows gives error code 6, which is translated
by cygwin to errno 9 = EBADF, and rsync then terminates.
rsync -avzuP foo roc:talks/
Even
rsync -r .
fails the same way, though it does not need a network
connection.
Steven Monai suggests that the problem may
at a dup2 after a fork in pipe.c (routine
piped_child). Windows gives error code 6, which is translated
by cygwin to errno 9 = EBADF, and rsync then terminates.
rsync -avzuP foo roc:talks/
Even
rsync -r .
fails the same way, though it does not need a network
connection.
Steven Monai suggests
On Sat, 2009-11-07 at 00:36 -0200, Carlos Carvalho wrote:
I use rsync -ii so that it logs *all* actions. Further, I don't use
any delete option but use --force. This means that if there's a name
collision rsync deletes files or directories. Here's an example:
0 0*deleting rwxrwsr-x
On Thu, 2009-11-05 at 09:20 -0500, Michael W. Cocke wrote:
What, exactly, does input/output error 5 mean? (Yes I googled it, but
all I can find is a lot of people getting the error, not what it means).
Typically, that there is something wrong with the filesystem or the
disk, which is out
Insufficient permissions
I am running a n rsync script on MAC OS 10.4 clients - runs OK with
a Windows 2003 server but getting this error when talking to an Apple
Server running OS X 10.5.7
It is a basic rsync as follows: copying, with sync from client to
server volume RETeensData
After a long stream of output that ends with (wrapped for mail):
rsync error: some files/attrs were not transferred (see previous
errors) (code 23) at main.c(1039) [sender=3.0.6]
How can I locate the above mentioned error in the output from:
/usr/bin/rsync -aCvv --stats
--exclude-from
https://bugzilla.samba.org/show_bug.cgi?id=6719
Summary: I/O error protection is broken w/ protocol 30 and
incremental recursion
Product: rsync
Version: 3.0.6
Platform: All
OS/Version: All
Status: NEW
Hi there,
I think IMHO that the description of the option --checksum-seed
should be :
--checksum-seed=NUM spécifie le grain de sable pour la somme de
contrôle
Or at least :
--checksum-seed=NUM spécifie le grain pour la somme de contrôle
But Not :
--checksum-seed=NUM spécifie la
201 - 300 of 1491 matches
Mail list logo
