Wayne Davison wrote: > On Fri, Aug 03, 2007 at 09:20:22PM +0200, [EMAIL PROTECTED] wrote: >> #0 0x00002b4167a93ee5 in free () from /lib64/libc.so.6 >> #1 0x0000000000431c9b in pool_free_old (p=0x66fb90, >> addr=<value optimized out>) at lib/pool_alloc.c:266 > > I found and fixed a bug in pool_free_old() that could leave some freed > extents on the list of currently allocated extents (in one code path). > If that were to happen, rsync would try to double-free the memory. > > Hopefully the latest version in CVS (and the "nightly" tar file) will > avoid this crash now.
Great! I've been experimenting with the incremental recursion in rsync 3.0-cvs to simplify our backup process for Wikipedia's uploaded media files -- about 2 TB in several million files, too big for rsync 2.x without breaking it up into a huge number of sub-invocations. I've been getting segfaults anywhere from a few minutes to a couple days into the copy, and the backtrace I managed to get seems to match this one. Thanks for the fix -- will let you know if we encounter any more problems. :) -- brion vibber (brion @ wikimedia.org) -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
