similar to: Rsync: Segmentation fault

Here's a resend of an old patch that is intended to avoid an infinite recursion (ending in a stack overflow) of the rwrite() function getting an error that calls rwrite(), ad naseum. I've only seen this happen when one of the sides dies due to a program error -- in that case, the connection is closed, and when we try to send an error to the other side and it generates an error, the error

in ocfs2_file_aio_write(), log_exit() could don't log the value which is really returned. this patch fixes it. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> --- fs/ocfs2/file.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c index 62442e4..a49fa44 100644 --- a/fs/ocfs2/file.c +++ b/fs/ocfs2/file.c @@ -1918,8

Hello, Noticed this (bug?) while testing out rsync. For a little background, I need to push files real-time to some front-end servers, and I am thinking of switching from some custom shell scripts that do this job to rsync. I am thinking of running rsync as a daemon on the front-end servers, and doing an upload from the back-end server to push the data out as it comes in. So, here is the deal:

(As I was composing this, the 2.6.1 release notice on the rsync list rolled in. The quoted source, below, hasn't changed, so I'll leave the 'pre-1' references unchanged...) I have a situation where an error message seems to be sent from the daemon to the client, but none is logged in the daemon's log. Daemon is 2.6.1pre-1, with --timeout=3600, light CPU load. Client is

Hi all, today we had a performance issue transfering a big amount of data where one file was over 50GB. Rsync was tunneled over SSH and we expected the data to be synced within hours. However after over 10 hours the data is still not synced ... The sending box has rsync running with 60-80 % CPU load (2GHz Pentium 4) while the receiver is nearly idle. So far I had no acces to the poblematic

-----BEGIN PGP SIGNED MESSAGE----- I added the following code to log_exit(): void log_exit(int code, const char *file, int line) { static int error_count=0; if(error_count++ > 10) { abort(); } To force it to bail earlier instead of overflowing the stack. As you can see at frame #50, it is trying to log that the connection went away unexpectantly.

I've compiled samba with the --with-ldapsam option and have setup up an ldap server. When I try to change the password of a user, say Administrator, get the following stuff with full debugging turned on (-D 255): New SMB password: Retype new SMB password: ldap_open_connection: connection opened ldap_connect_system: succesful connection to the LDAP server ldap_search_one_user: searching

https://bugzilla.samba.org/show_bug.cgi?id=3271 Summary: Rsync instances stay in memory when using in daemon mode Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Hi everyone I'm still getting strange sizes on the daemon logs. After transferring around 1.66GB over 14 hours (256kbit link) to an absolutely empty directory, I get: 2007/01/26 04:13:43 [26441] sent 57014 bytes received 44708 bytes total size 1947222268 du reports the final size of the directory on the daemon side as 1.6 G, and the "received" bytes can't be 44708?! I know

https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com

Hi all, I just had a panic with dovecot 1.1.6, two days after replacing 1.0.15 with it in production. Here are the logs immediately preceding the panic, I think they're related. It seems the user connected simultaneously from two different clients, from his own computer and a webmail running on the server, then manipulated mail folders on one side, and logged out. The panic occurred 3

Here's an oops output on 2.4.5 + CVS/ext3. This happened while trying to do a mkinitrd (on RedHat 7.1). ksymoops 2.4.0 on i686 2.4.5-2smp. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.5-2smp/ (default) -m /boot/System.map-2.4.5-2smp (specified) kernel BUG at inode.c:934! invalid operand: 0000 CPU: 1 EIP:

(I am not on the rsync mailing list, so if you send a response to this message to the list, please be sure to CC me.) I first reported this bug go Red Hat in <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65350>. If you run rsync with a subshell through ssh.com's ssh and sshd and then kill the client with ctrl-C, the rsync server process running on the remote machine grows

As I reported a while back rsync doesn't handle metadata (permissions and ownership) in dryrun mode. I offered to make a patch and that offer still stands. I didn't have the time for it until now and want to pick it up again. I had some ugly hack back then but I want to redo it in a clean way. I would like some input on my thoughts. IMHO, it would be ideally if the check for dry_run

rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with

Hi, I am using the db backend for the expire plugin and found the following error message in the logfile: dovecot: Jan 22 10:10:55 Error: dict: secondary db: unable to allocate space from the buffer cache dovecot: Jan 22 10:10:55 Error: dict: Failed to initialize dictionary 'expire' dovecot: Jan 22 10:10:55 Error: IMAP(xxxxxxxxxx): read(/var/dovecot/dict-server) failed: Remote

I upgraded from Samba 3.0.20 to 3.0.21a last night on my Solaris 10 machine. After the upgrade, everything seemed to work fine, but I see that Samba is panic'ing in the logs. As far as I can tell, the client retries whatever it was doing and succeeds (at least, we've had no reports of problems from our users). I have attached a level 10 debug, backtrace, and my smb.conf. The

People of cygwin & rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a "get" (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going

=3Cbody=3E =3Cp class=3D=22MsoNormal=22=3E=3Ci=3E=3Cspan lang=3D=22EN-US=22 style=3D=22font-size=3A 10=2E0pt=3B mso-bidi-font-size=3A 12=2E0pt=22=3E=3Cfont face=3D=22Verdana=22=3Eplease note to send ALL REPLY e-mail direct to me at=3A =3Ca href=3D=22mailto=3AQuestions=40QualityWatchWorld=2Ecom=22=3EQuestions=40QualityWatchWorld=2Ecom=3C=2Fa=3E=3Co=3Ap=3E =3C=2Fo=3Ap=3E

The saga continues. I've been tracking the interface changes and merging them with the refactoring work I'm doing. I got as far as building stage3 of llvm-gcc but the object files from stage2 and stage3 differ: warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs (Are the above two ok?) The list below is clearly bad. I think it's every object file in the