[Bug 15585] New: rsync ends still with error 22 when try to deleting many files

https://bugzilla.samba.org/show_bug.cgi?id=15585 Bug ID: 15585 Summary: rsync ends still with error 22 when try to deleting many files Product: rsync Version: 3.2.0 Hardware: All OS: All Status

Re: Everything working as expected, so shouldn't ERROR be WARNING

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 sp

Re: Everything working as expected, so shouldn't ERROR be WARNING

up by using this command on the local machine titan: > > rprice@titan ~ rsync -av --dry-run /mnt/home/rprice > rsync://rprice@maria/rprice-home > > I get the messages > > sending incremental file list > ERROR: daemon refused to receive file "rprice/demo.dvi" >

Everything working as expected, so shouldn't ERROR be WARNING

/home/rprice rsync://rprice@maria/rprice-home 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 requested that dvi files not be trans

rsync error messages always in English (= never translated)?

I want to recognize and handle some rsync error messages in my log files (containing also the --itemize-changes output) on different computers with different language/locale settings. Can I rely on rsync to create only English error messages to have a stable pattern to recognize? PS

Uncorrectable bit error handling by rsync?

Suppose rsync on one system is used to synchronize files to another system. Further, suppose rsync encounters an uncorrectable bit error reading a file that is being transferred. What's the chances that rsync corrupts the file on the other system? Thanks, John -- John Conover

Re: Build error on Solaris 10

On Tue, Sep 20, 2022 at 11:21 AM İhsan Doğan via rsync < rsync@lists.samba.org> wrote: > ./mkgitver > ./mkgitver: test: argument expected > Looks like your OS's "test" doesn't support "-e". If you tweak the "if [ -e" to be "if [ -d" you should be fine. ..wayne.. -- Please use reply-all for

Build error on Solaris 10

Hi, While rsync 3.2.5 was building fine on Solaris 10, I’m running into this error with 3.2.6: /opt/SUNWspro/bin/cc -I. -I. -I./zlib -xO3 -m32 -xarch=sparc -DHAVE_CONFIG_H -I/opt/csw/include -c uidlist.c -o uidlist.o /opt/SUNWspro/bin/cc -I. -I. -I./zlib -xO3 -m32 -xarch=sparc -DHAVE_CONFIG_H

Re: 3.2.6: ERROR: rejecting unrequested file-list

On Tue, Sep 13, 2022 at 9:06 AM Carlos Carvalho wrote: > The debug option didn't change the output at all. > That seems quite unlikely to me. But ignoring that, the latest git should hopefully have the issue you're seeing fixed. Rsync packagers will want this newest commit

Re: 3.2.6: ERROR: rejecting unrequested file-list

y in the update list. Here are 2 samples: ERROR: rejecting unrequested file-list name: distrib/cauldron/SRPMS/core/release/media_info rsync error: protocol incompatibility (code 2) at flist.c(998) [Receiver=3.2.6] ERROR: rejecting unrequested file-list name: distribution/leap rsync

Re: 3.2.6: ERROR: rejecting unrequested file-list

It helps to have some kind of a reproducer. Also, keep in mind there are 2 kinds of rejections: unrequested args and unfiltered files. The latter should have a big improvement in the latest git version. If you want some debug info on arg rejection, try adding `--debug=filter5` and see what

3.2.6: ERROR: rejecting unrequested file-list

I've just upgraded the Debian package to 3.2.6 and now I'm getting many cases of this error. I see that there have been improvements in the check but it seems they're either not enough or incompatible with 3.1.[23]. This is always with --files-from, used for mirroring. We're a large free software

Re: Patch: more detailed error logging when an ACL unpack error occurs

On Sat, Sep 10, 2022 at 1:29 PM Ryan Schmidt wrote: > Would you be interested in adding this patch to the rsync-patches repo or > incorporating it into rsync directly? > I don't recall seeing that before, so thanks for pointing that out. I've committed the change to the rsync git. ..wayne.. --

Patch: more detailed error logging when an ACL unpack error occurs

Hi, I maintain the rsync port in MacPorts. For ten years, we've been carrying around a one-line patch which was described by its contributor this way: > Occasionally, sync will report an ACL unpack error, but the user will be left > in the dark regarding which file(s) was affected. Thi

Invalid dir index: -826 (-101 - -825) [receiver] -- rsync error: protocol incompatibility (code 2) at rsync.c(370) [receiver=3.2.5]

Hi, folk. I got some problem when running this command on client side: # rsync -avPH --chown=root:wheel --chmod=D755,F644 --delete --exclude ads --exclude backup rsync://192.168.0.100/data /mnt/DATA receiving incremental file list Invalid dir index: -826 (-101 - -825) [receiver] rsync error

Re: deflate on token returned 0 - rsync error: error in protocol data stream

tes left) > rsync error: error in rsync protocol data stream (code 12) at token.c(427) > [sender=3.1.3] I manged to create a reproducer: https://code.schlittermann.de/heiko/rsync-bug/src/commit/d8176333f8ef08b7dbf7957c83055677cddcc080/bug Several times in a row if successfully reproduce

deflate on token returned 0 - rsync error: error in protocol data stream

Hello, we're using rsync on SLES 12 SP 5 on both sides (for detailed version info see below) and we're experiencing the following issue on the sender's side: ``` etc/test/windows2019_x86_64_20210929.gz deflate on token returned 0 (22199 bytes left) rsync error: error in rsync protocol data

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #14 from Roland Haberkorn --- After the new version made it into my system I can confirm it works like a charm. Many thanks for the effort. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use

Skip file transfer on detecton of error code

xposn/newsci/2011/n2809.pdf": Input/output error (5)-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Getting error code 12 when using rsync with ssh in RHEL 8

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

Re: Copying TBs -> error -> work around

Ctrl-C to interrupt ipos:9253 MB, non-trimmed:0 B, current rate: 0 B/s opos:9253 MB, non-scraped:0 B, average rate: 37768 kB/s non-tried:7849 GB, bad-sector:0 B,error rate: 0 B/s rescued:9253 MB, bad areas:0,run

Re: Copying TBs -> error -> work around

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

Re: Copying TBs -> error -> work around

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

Re: Copying TBs -> error -> work around

>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

Copying TBs -> error -> work around

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

[Bug 14463] rsync 3.2.2 server protocol error

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

[Bug 14463] rsync 3.2.2 server protocol error

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

[Bug 14463] rsync 3.2.2 server protocol error

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

[Bug 14463] rsync 3.2.2 server protocol error

https://bugzilla.samba.org/show_bug.cgi?id=14463 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 14463] New: rsync 3.2.2 server protocol error

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

[Bug 14076] 3.13 - lib/sysacls.h:118:13: error: array type has incomplete element type 'struct acl'

https://bugzilla.samba.org/show_bug.cgi?id=14076 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 11654] Misleading error message

|--- |WORKSFORME --- Comment #2 from Wayne Davison --- I don't see that error in that scenario. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options

[Bug 10372] rsync 3.10 error in protocol data stream while rsync 3.0.9 runs through

https://bugzilla.samba.org/show_bug.cgi?id=10372 Wayne Davison changed: What|Removed |Added CC||m...@gromco.com --- Comment #15 from

[Bug 10579] --xattr internal abbrev error

https://bugzilla.samba.org/show_bug.cgi?id=10579 Wayne Davison changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

Re: rsync error

t;files[0] * flist->malloced), > (new_ptr == flist->files) ? " not" : ""); > } > It's not an error of any sort, and you're only seeing it because you've enabled DEBUG_GTE. Is there some other problem that you're trying to debug? .Dave. -- Ple

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

unexpected and many people will have a long running rsync command (for me each try took ~6hrs until I could reproduce the error) fail on them until they could even be aware that there is such a limit. In addition to that, I guess only a small fraction of those people will probably find this parameter

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

|RESOLVED --- Comment #12 from Wayne Davison --- I fixed the allocation args to be size_t values (and improved a bunch of allocation error checking while I was at it). I then added an option that lets you override this allocation sanity-check value. The default is still 1G per

rsync error

Hello everybody, I am having a funny problem while using rsync as a tool to back-up my files: [sender] expand file_list pointer array to 524288 bytes, did move. I am just wondering if you had this issue before and if you know a way to solve this, please share with me. Many thanks, Dr.

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #11 from MulticoreNOP --- I want to add that the original implementation also leads to the following error: ERROR: out of memory in flist_expand [sender] rsync error: error allocating core memory buffers (code 22) at util2.c(106

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #10 from MulticoreNOP --- (In reply to Simon Matter from comment #7) #define MALLOC_MAX 0x1 is greater than uint32-MAX, therefore will overflow and result in an unpredictable and unfriendly manner. #define MALLOC_MAX

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 MulticoreNOP changed: What|Removed |Added CC||multicore...@mailbox.org --- Comment #9

[Bug 10579] --xattr internal abbrev error

wanted to note that this issue can still occur, and I'm still at a bit of a loss as to what is causing it; it's being reported as a protocol error, but it can happen even when performing a transfer locally (no possibility of a version mismatch). -- You are receiving this mail because: You

[Bug 12838] [PATCH] Log sent/received bytes even in case of error

https://bugzilla.samba.org/show_bug.cgi?id=12838 Ben RUBSON changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 12522] [PATCH] Send last error messages to sender

https://bugzilla.samba.org/show_bug.cgi?id=12522 Ben RUBSON changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #8 from Roland Haberkorn --- Is it possible to totally get rid of the restriction? I'd prefer running in out of memory situations rather than in this restriction. Without I could just throw some more RAM on the machine, with this

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #7 from Simon Matter --- I've patches like this to solve our issues: --- rsync-3.1.3/util2.c.orig2018-01-15 04:55:07.0 +0100 +++ rsync-3.1.3/util2.c2020-03-11 13:07:07.138141415 +0100 @@ -59,7 +59,7 @@ return

[Bug 14214] New: --report-special=OPS option to return error code if no data was copied

https://bugzilla.samba.org/show_bug.cgi?id=14214 Bug ID: 14214 Summary: --report-special=OPS option to return error code if no data was copied Product: rsync Version: 3.1.3 Hardware: All OS: All

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #6 from Dave Gordon --- The hash table doubles each time it reaches 75% full. A hash table for 32m items @ 16 bytes each (8 byte key, 8 byte void *data) needs 512MB of memory. At the next doubling (up to 64m items) it hits the array

Re: [Bug 12769] error allocating core memory buffers (code 22) depending on source file system

On 11/10/2019 13:53, just subscribed for rsync-qa from bugzilla via rsync wrote: > https://bugzilla.samba.org/show_bug.cgi?id=12769 > > --- Comment #5 from Simon Matter --- > I'm suffering the same problem and was wondering if anyone found a solution or > work around or other tool to do the job?

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #5 from Simon Matter --- I'm suffering the same problem and was wondering if anyone found a solution or work around or other tool to do the job? First I thought maybe it's a bug which is fixed already and tried with the latest release

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #4 from Ovidiu Stanila --- We hit the same issue on a CentOS 6 server (kernel 2.6.32-754.18.2.el6.x86_64), the sync would break with the following error: # /usr/bin/rsync --debug=HASH --stats --no-inc-recursive -aHn --delete /app

[Bug 14076] 3.13 - lib/sysacls.h:118:13: error: array type has incomplete element type 'struct acl'

https://bugzilla.samba.org/show_bug.cgi?id=14076 --- Comment #1 from Jari Aalto --- Created attachment 15375 --> https://bugzilla.samba.org/attachment.cgi?id=15375=edit Cygwin x64 config.status -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use

[Bug 14076] New: 3.13 - lib/sysacls.h:118:13: error: array type has incomplete element type 'struct acl'

https://bugzilla.samba.org/show_bug.cgi?id=14076 Bug ID: 14076 Summary: 3.13 - lib/sysacls.h:118:13: error: array type has incomplete element type 'struct acl' Product: rsync Version: 3.1.3 Hardware: x64 OS

Multiple errors from rsync - later 'soft' error raised rather than earlier 'hard' error.

Peter, I was about to post the below to the rsync mailing list, but wondered whether your code which captures rsync output may have allowed rsync to continue past what I think would normally be a fatal error? Thanks Rob. P.S. Should I put the final backups of the old pearcey /home back

[Bug 13953] New: error message instead of --stats informations (in case of vanished files), using rsync 3.1.1 and rsync 3.0.9

https://bugzilla.samba.org/show_bug.cgi?id=13953 Bug ID: 13953 Summary: error message instead of --stats informations (in case of vanished files), using rsync 3.1.1 and rsync 3.0.9 Product: rsync Version: 3.1.1 Hardware

[Bug 13656] New: --link-dest target with symbolic links from different user produces unnecessary error

https://bugzilla.samba.org/show_bug.cgi?id=13656 Bug ID: 13656 Summary: --link-dest target with symbolic links from different user produces unnecessary error Product: rsync Version: 3.1.3 Hardware: All OS

[Bug 12522] [PATCH] Send last error messages to sender

solete|| --- Comment #3 from Ben RUBSON <ben.rub...@gmail.com> --- Created attachment 13959 --> https://bugzilla.samba.org/attachment.cgi?id=13959=edit Send last error messages to sender Modified patch to seamlessly suit rsync 3.1.3. Thx ! -- You are rece

[Bug 11215] compression/zlib errors discard the zlib error message

https://bugzilla.samba.org/show_bug.cgi?id=11215 --- Comment #2 from George --- Anyone experiencing a similar issue may want to have a look at bug 10372 . ( Possibly related: bug 10332. ) -- You are receiving this mail because: You are the QA Contact for the bug. --

[Bug 1442] rsync sender appears to hang when receiver recounters an error

https://bugzilla.samba.org/show_bug.cgi?id=1442 --- Comment #13 from devuran...@gmx.net --- There are a lot of bugreports related to rsync hanging mysteriously, some of which may be duplicates of each other: https://bugzilla.samba.org/show_bug.cgi?id=1442

[Bug 10719] Error with cached effective process gid

https://bugzilla.samba.org/show_bug.cgi?id=10719 Wayne Davison changed: What|Removed |Added Resolution|--- |FIXED

[Bug 10719] Error with cached effective process gid

https://bugzilla.samba.org/show_bug.cgi?id=10719 --- Comment #1 from lonerr --- Three years later, any updates? :) -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To

rename error on temporary destination file

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

Re: hard-link reference error when trying to delete

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="rsync --server

Re: hard-link reference error when trying to delete

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="rsync --server -vulogDtpre.iLsfxC --timeout=600 --bwlimit=5120 . dest" ssh-rsa Tacking on --delete in the

Re: hard-link reference error when trying to delete

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

hard-link reference error when trying to delete

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

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

sspc25:~$ rsync -rlptgoDxHAn --info=name,progress2 --delete --link-dest=/mnt2/link3/ /mnt/rsynctestsource/ /mnt2/link1/. 0 100%0.00kB/s0:00:00 (xfr#0, ir-chk=1000/25191050) ERROR: out of memory in hashtable_node [sender] rsync error: error allocating core memory buffers (code 22) at

[Bug 12838] [PATCH] Log sent/received bytes even in case of error

https://bugzilla.samba.org/show_bug.cgi?id=12838 --- Comment #1 from Ben RUBSON --- Mmmmh unfortunately numbers are not correct. # Sender side (which interrupts the transfer receiving SIGUSR2) : Total file size: 16­.85G bytes Total transferred file size: 183­.38M bytes

[Bug 12838] New: [PATCH] Log sent/received bytes even in case of error

https://bugzilla.samba.org/show_bug.cgi?id=12838 Bug ID: 12838 Summary: [PATCH] Log sent/received bytes even in case of error Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #2 from Roland Haberkorn --- I did some further investigation... First thing to add: The ext4 file systems are hard-linked differential rsync backups of the real data on XFS. I changed the testcase by deleting the

[Bug 12769] error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 --- Comment #1 from Roland Haberkorn --- If you want me to run further testings with other file systems I am totally willing to produce fake data and run tests. I just haven't done yet because of my lack of knowledge about the

[Bug 12769] New: error allocating core memory buffers (code 22) depending on source file system

https://bugzilla.samba.org/show_bug.cgi?id=12769 Bug ID: 12769 Summary: error allocating core memory buffers (code 22) depending on source file system Product: rsync Version: 3.1.0 Hardware: All OS: Linux

Re: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]

> 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

Re: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]

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

Re: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]

ms to have made it through 10 before failing again overnight: 66596 20:38:03 rsync -vP -iaHJAX `cat /tmp/unback` /Volumes/platinum-barratry/x/Backups.backupdb/pb3/ ... rsync: unpack_smb_acl: sys_acl_get_info(): Undefined error: 0 (0) rsync: unpack_smb_acl: sys_acl_get_info(): Undefined error: 0 (0)

error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]

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

[Bug 12522] [PATCH] Send last error messages to sender

solete|| --- Comment #2 from Ben RUBSON <ben.rub...@gmail.com> --- Created attachment 12841 --> https://bugzilla.samba.org/attachment.cgi?id=12841=edit Send last error messages to sender Error correction on sender side. -- You are receiving this mail because:

[Bug 12522] New: [PATCH] Send last error messages to sender

https://bugzilla.samba.org/show_bug.cgi?id=12522 Bug ID: 12522 Summary: [PATCH] Send last error messages to sender Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal

Re: segfault at 968 Error

>>> vigneshdhanra...@gmail.com> wrote: >>> >>>> Hi Team, >>>> >>>> While Running rsync rsync://username@ip:873 , I am getting following >>>> error. >>>> >>>> rsync: safe_read failed to read 1 bytes [Receiver]: Conn

Re: segfault at 968 Error

>> Any update on this issue. >> >> On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G < >> vigneshdhanra...@gmail.com> wrote: >> >>> Hi Team, >>> >>> While Running rsync rsync://username@ip:873 , I am getting following >>> e

Re: segfault at 968 Error

gt; >> Hi Team, >> >> While Running rsync rsync://username@ip:873 , I am getting following >> error. >> >> rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset >by >> peer (104) >> rsync error: error in rsync protocol data str

Re: segfault at 968 Error

Any update on this issue. On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G < vigneshdhanra...@gmail.com> wrote: > Hi Team, > > While Running rsync rsync://username@ip:873 , I am getting following > error. > > rsync: safe_read failed to read 1 bytes [Receiver]: Connect

segfault at 968 Error

Hi Team, While Running rsync rsync://username@ip:873 , I am getting following error. rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(276) [Receiver=3.1.1] In Remote pc , i can see segmentation

Re: error code 255 - not mentioned in manpage?

On Tue 25 Oct 2016, devz...@web.de wrote: > > is there a reason why error code 255 is not mentioned in the manpage > and wouldn`t it make sense to add "255 Unexplained Error" there > for completeness ? It wouldn't be unexplained then anymore, would it? :-) Paul --

error code 255 - not mentioned in manpage?

hi, is there a reason why error code 255 is not mentioned in the manpage and wouldn`t it make sense to add "255 Unexplained Error" there for completeness ? I`m writing a script which checks exit values and while testing it, i got value 255, looked into the manpage and scratch

[Bug 12132] New: Error on attributes when directory read-only

https://bugzilla.samba.org/show_bug.cgi?id=12132 Bug ID: 12132 Summary: Error on attributes when directory read-only Product: rsync Version: 3.1.2 Hardware: All OS: Mac OS X Status: NEW Severity: normal

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 Armin Mohring changed: What|Removed |Added Resolution|--- |FIXED

[Bug 11654] New: Misleading error message

https://bugzilla.samba.org/show_bug.cgi?id=11654 Bug ID: 11654 Summary: Misleading error message Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5

[Bug 11654] Misleading error message

https://bugzilla.samba.org/show_bug.cgi?id=11654 --- Comment #1 from Taso Hatzi <taso.ha...@gmail.com> --- rsync bombs with "rsync error: syntax or usage error (code 1) at main.c(873) [Receiver=3.1.1]" if it doesn't have write permissions on the destination. This is som

Re: Command Failed -1 error

Hello, In the past and present we have received an error of "Command failed with -1:" when running rsync. -1 is not a valid response that I can find. Is there a way to debug this or has anyone come across a -1 error? We receive messages with a 12, 23, 24 which makes sense b

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

ernal USB3.0 drive with 2TB. If the drive is not mounted, the following error occurs: rsync error: error in file io (code 11) at main.c (656) [Receiver=3.1.1] Improvemnt suggestion: Rsync should detect, if the drive is mounted or not. -- You are receiving this mail because: You are th

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 --- Comment #7 from Kevin Korb --- Rsync has no idea (or way) to know that you are trying to rsync to a separate disk. You give it a source and a target and it uses what is there. If you need to check for a mounted

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 --- Comment #9 from Kevin Korb --- You have no idea how many people would complain if rsync didn't create a non-existing target directory. It is already a very common complaint that rsync won't create more than one deep. --

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 --- Comment #8 from Armin Mohring <armin_mohr...@web.de> --- Why should rsync that know. There is an error, if the specified folder does not exist. Could be an external disk or partition or something else. -- You are receiving this mail b

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 Armin Mohring changed: What|Removed |Added Resolution|--- |INVALID

[Bug 11578] New: Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 Bug ID: 11578 Summary: Rsync does start with an error directly connecting an USB drive to a port Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

ent #1 from Armin Mohring <armin_mohr...@web.de> --- error output: rsync error: error in file io (code 11) at main.c (656) [Receiver=3.1.1] This error occurs, when I connect an USB drive [USB HDD, 2TB) to an USB 3.0 port and try to start an incremental file transfer. -- You are receivi

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 --- Comment #2 from Kevin Korb --- There should be additional errors. If not from rsync then from dmesg. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 --- Comment #3 from Armin Mohring --- This is the relevant part from dmesg after connecting the drive to an USB 3.0 port: 5773.601144] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 5777.829686] usb 4-3: new SuperSpeed

[Bug 11578] Rsync does start with an error directly connecting an USB drive to a port

https://bugzilla.samba.org/show_bug.cgi?id=11578 --- Comment #4 from Kevin Korb --- There are no device, block, or filesystem errors after that? -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid

  1   2   3   4   5   6   7   8   9   10   >