Re: rsync on newer kernel does not quite work?
On Mon, Feb 19, 2001 at 11:09:33PM +0100, Rasmus Andersen wrote: [...] (I'll just continue talking to myself in the hope that somebody will read this and be inspired.) In order to clear things up I should clearly state that my rsync problem manifests itself under local operation. Ie., 'rsync -arv linux-242p4/ linux' will hang. No network is involved and the problem does not manifest itself under 2.2.X kernels with the exact same dataset. Also, I have played around with strace and discovered that if I make strace follow the children too the hang goes away. So 'strace rsync -arv linux-242p4/ linux' hangs (in wait4, btw) while 'strace -f rsync -arv linux-242p4/ linux' does not. I hope this will mean something to somebody. I can put up strace output on the net if anybody profess any interest. -- Regards, Rasmus([EMAIL PROTECTED]) "There are also enough rocks on Earth to kill the world's population several times over." -- Lt. General Daniel Graham, DIA, explaining why it's necessary to have more than enough nukes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: rsync on newer kernel does not quite work?
On Mon, Feb 19, 2001 at 11:09:33PM +0100, Rasmus Andersen wrote: [...] (I'll just continue talking to myself in the hope that somebody will read this and be inspired.) In order to clear things up I should clearly state that my rsync problem manifests itself under local operation. Ie., 'rsync -arv linux-242p4/ linux' will hang. No network is involved and the problem does not manifest itself under 2.2.X kernels with the exact same dataset. Also, I have played around with strace and discovered that if I make strace follow the children too the hang goes away. So 'strace rsync -arv linux-242p4/ linux' hangs (in wait4, btw) while 'strace -f rsync -arv linux-242p4/ linux' does not. I hope this will mean something to somebody. I can put up strace output on the net if anybody profess any interest. -- Regards, Rasmus([EMAIL PROTECTED]) "There are also enough rocks on Earth to kill the world's population several times over." -- Lt. General Daniel Graham, DIA, explaining why it's necessary to have more than enough nukes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
rsync on newer kernel does not quite work?
Hi. For some time up through the testX kernels I used rsync to update my "dirty" tree after applying the latest patches to the clean tree. At some point this stopped working (more about that later) but as new kernels were coming fast at that time I did not think much of it, assuming that cleverer folk than me would fix it soon. They did not, however, and I got kinda used to working around the "bug". The problem manifests itself in that rsync will complete syncing two directories but will then hang (soft). It can be killed with ^C and rerun with success. The amount of work that rsync needs to do seems to be the trigger: rsyncing the drivers directory (to a non-existent dir) will trigger the hang for me, but drivers/[a-r]* will not. Since Matthias Schniedermeyer reported the same problem in http://marc.theaimsgroup.com/?l=linux-kernel=98157768131423=2 I have tried on and off to locate the kernel version where the shift in behaviour happened, but after recompiling all kernels down to test1 I have not gotten a successfull rsync run yet. And I am sure that it worked once, well after test1. I have upgraded my build environment from RH6.2 to RH7.0 in the meanwhile, but I even remembered to change 'gcc' to 'kgcc' in the makefile without luck :/ However, rsync behaves as expected under 2.2.18 (compiled locally) and the 2.2.16-22 that comes with RH7.0. But not under any of the 2.4.X kernels that I have tried (most of them incl. -acX). rsyncs tried: 2.4.4-1 (rpm), 2.4.6 (local compile) and 2.4.1 (ditto). kernels tried (not working) (partial list): 241, 241ac9, 242p4, 240-testX (1<=X<=12). gccs tried (rsync and kernel compiles): kgcc (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)), gcc (gcc version 2.96 2731 (Red Hat Linux 7.0)) (2.96-69) If you need further information please let me know. -- Regards, Rasmus([EMAIL PROTECTED]) First snow, then silence. This thousand dollar screen dies so beautifully. --- Error messages in haiku - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
rsync on newer kernel does not quite work?
Hi. For some time up through the testX kernels I used rsync to update my "dirty" tree after applying the latest patches to the clean tree. At some point this stopped working (more about that later) but as new kernels were coming fast at that time I did not think much of it, assuming that cleverer folk than me would fix it soon. They did not, however, and I got kinda used to working around the "bug". The problem manifests itself in that rsync will complete syncing two directories but will then hang (soft). It can be killed with ^C and rerun with success. The amount of work that rsync needs to do seems to be the trigger: rsyncing the drivers directory (to a non-existent dir) will trigger the hang for me, but drivers/[a-r]* will not. Since Matthias Schniedermeyer reported the same problem in http://marc.theaimsgroup.com/?l=linux-kernelm=98157768131423w=2 I have tried on and off to locate the kernel version where the shift in behaviour happened, but after recompiling all kernels down to test1 I have not gotten a successfull rsync run yet. And I am sure that it worked once, well after test1. I have upgraded my build environment from RH6.2 to RH7.0 in the meanwhile, but I even remembered to change 'gcc' to 'kgcc' in the makefile without luck :/ However, rsync behaves as expected under 2.2.18 (compiled locally) and the 2.2.16-22 that comes with RH7.0. But not under any of the 2.4.X kernels that I have tried (most of them incl. -acX). rsyncs tried: 2.4.4-1 (rpm), 2.4.6 (local compile) and 2.4.1 (ditto). kernels tried (not working) (partial list): 241, 241ac9, 242p4, 240-testX (1=X=12). gccs tried (rsync and kernel compiles): kgcc (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)), gcc (gcc version 2.96 2731 (Red Hat Linux 7.0)) (2.96-69) If you need further information please let me know. -- Regards, Rasmus([EMAIL PROTECTED]) First snow, then silence. This thousand dollar screen dies so beautifully. --- Error messages in haiku - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
