Weird problem with rsync 3.0.9
Hi all, I'm not sure if this is really rsync related so fell free to ignore this message ;) I have to server. The first one is rsync server et and the second one the client. The rsync server repo is around 325Go. Every time my client start rsync, both rsyncd on the server and rsync on the client entered Uninterruptible sleep state and I can't figure out why. Server : - Linux san1 2.6.30-gentoo-r4 #3 SMP Thu Nov 19 14:17:42 CET 2009 x86_64 Intel(R) Xeon(R) CPU E5405 @ 2.00GHz GenuineIntel GNU/Linux - 8Gb ECC RAM - Rsync server : 3.0.9 - Rsyncd.conf : # /etc/rsyncd.conf pid file = /var/run/rsyncd.pid use chroot = no read only = yes transfer logging = no dont compress = * timeout = 60 [webroot] path = /home/http comment = Webroot Tree uid = root gid = webusers Client : - Linux san2 3.2.12-gentoo #1 SMP Mon May 14 13:50:17 CEST 2012 x86_64 Intel(R) Xeon(R) CPU E5405 @ 2.00GHz GenuineIntel GNU/Linux - 8Gb ECC RAM - Rsync client : 3.0.9 Network is 1Gbps dedicated. FS on both server is ext3. I've tried to get a call trace for blocking process and this is what I have : echo w /proc/sysrq-trigger ; dmesg -c foo cat foo Server : [902361.152155] SysRq : Show Blocked State [902361.152382] taskPC stack pid father [902361.152401] rsync D 8800280daa40 0 15001 14596 [902361.152406] 88022f0c8630 0086 8800cf54e400 8800188ef600 [902361.152410] 00010a40 c5e8 88022d91d070 88022d91d308 [902361.152414] 00062dd1dee0 8114238b 88022d91d308 000135c45c5c [902361.152418] Call Trace: [902361.152427] [8114238b] ? elv_next_request+0x18f/0x1a3 [902361.152432] [810bfa3e] ? sync_buffer+0x0/0x40 [902361.152436] [812f7090] ? schedule+0x9/0x1d [902361.152439] [812f7107] ? io_schedule+0x63/0xa5 [902361.152442] [810bfa3e] ? sync_buffer+0x0/0x40 [902361.152445] [810bfa79] ? sync_buffer+0x3b/0x40 [902361.152448] [812f7431] ? __wait_on_bit+0x41/0x70 [902361.152452] [810bfa3e] ? sync_buffer+0x0/0x40 [902361.152454] [812f74cb] ? out_of_line_wait_on_bit+0x6b/0x77 [902361.152460] [810444d8] ? wake_bit_function+0x0/0x23 [902361.152464] [810f6177] ? ext3_bread+0x4c/0x6d [902361.152468] [810faa22] ? htree_dirblock_to_tree+0x33/0x13e [902361.152472] [810b0655] ? dput+0x23/0x13d [902361.152475] [810faba9] ? ext3_htree_fill_tree+0x7c/0x1e7 [902361.152479] [8109d927] ? __kmalloc+0xf2/0x102 [902361.152483] [810f20d1] ? ext3_readdir+0x173/0x554 [902361.152486] [810ae180] ? filldir+0x0/0xb7 [902361.152490] [810a56e3] ? cp_new_stat+0xe9/0xfc [902361.152493] [810ae180] ? filldir+0x0/0xb7 [902361.152496] [810ae33f] ? vfs_readdir+0x75/0xa7 [902361.152499] [810ae4a9] ? sys_getdents+0x7a/0xc1 [902361.152503] [8100b9eb] ? system_call_fastpath+0x16/0x1b echo w /proc/sysrq-trigger ; dmesg -c foo cat foo Client : [ 4660.188240] SysRq : Show Blocked State [ 4660.188460] taskPC stack pid father [ 4660.188474] rsync D 0 5846 5840 0x [ 4660.188479] 8802260855c0 0086 880221e7e010 88022628ee40 [ 4660.188484] 00010280 880221e7ffd8 880221e7ffd8 00010280 [ 4660.188488] 8802251f2210 88022628ee40 8802251f25a0 8802251f2210 [ 4660.188492] Call Trace: [ 4660.188502] [8114c19b] ? blk_peek_request+0x17c/0x18e [ 4660.188507] [811e8363] ? scsi_request_fn+0x31e/0x3f7 [ 4660.188511] [8114d20e] ? blk_queue_bio+0x273/0x28c [ 4660.188515] [810cc6ba] ? unmap_underlying_metadata+0x29/0x29 [ 4660.188520] [8133367e] ? io_schedule+0x89/0xc9 [ 4660.188523] [810cc6c3] ? sleep_on_buffer+0x9/0xe [ 4660.188526] [81333a42] ? __wait_on_bit+0x41/0x70 [ 4660.188529] [810cc6ba] ? unmap_underlying_metadata+0x29/0x29 [ 4660.188533] [81333adc] ? out_of_line_wait_on_bit+0x6b/0x77 [ 4660.188537] [81043413] ? autoremove_wake_function+0x2e/0x2e [ 4660.188541] [810cc788] ? ll_rw_block+0x65/0x82 [ 4660.188545] [81105592] ? ext3_bread+0x49/0x68 [ 4660.188548] [8110a302] ? htree_dirblock_to_tree+0x33/0x126 [ 4660.188552] [8110a46e] ? ext3_htree_fill_tree+0x79/0x1d3 [ 4660.188557] [810b5cb7] ? do_last+0x527/0x59e [ 4660.188561] [81101b36] ? ext3_readdir+0x179/0x532 [ 4660.188564] [810b813c] ? filldir64+0xb0/0xb0 [ 4660.188567] [810ae253] ? cp_new_stat+0xe9/0xfb [ 4660.188570] [810b813c] ? filldir64+0xb0/0xb0 [ 4660.188573] [810b82ea] ? vfs_readdir+0x72/0xa4 [ 4660.188576] [810b8454] ? sys_getdents+0x7a/0xc1 [ 4660.188580]
[Bug 8941] New: Solved problem with hard links and schg flag
https://bugzilla.samba.org/show_bug.cgi?id=8941 Summary: Solved problem with hard links and schg flag Product: rsync Version: 3.0.9 Platform: All OS/Version: FreeBSD Status: NEW Severity: major Priority: P5 Component: core AssignedTo: way...@samba.org ReportedBy: fr...@electromail.org QAContact: rsync...@samba.org Created attachment 7559 -- https://bugzilla.samba.org/attachment.cgi?id=7559 Patch for syscall.c Hi! Using rsync under FreeBSD with hard links and files having schg set result in EPERM Operation not permitted. This behavior can be observed if rsyncing /usr/bin/. The patch fileflags.diff tries to deal with this situation but changes the flags of the parent directory only. It doesn't change the flags of the files itself. do_link() in syscall.c has to be fixed. patch-syscall.c.txt is a patch which have the be applied after fileflags.diff. Best regards Franz -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- 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: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Patches for OS X.
What patch files are necessary to build rsync-3.0.9 for OS X 10.6.8 (Darwin 10.8.0)? Mr. Bombich maintains an excellent page about this, but it's a bit out of date, methinks, and his instructions point to patch files that return some interesting errors. My rsync-3.0.9 is working just fine, btw, with the fileflags and crtimes and hfs-compression patches applied; I just wondered if the others that he mentioned are needed. http://www.bombich.com/rsync.html This is a very useful site that Mr. B. has maintained for several years -- thanks! -- Tony Reed anthony.r...@gmail.com -- 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
