similar to: [Bug 3186] New: Surprisingly large unshared memory usage

https://bugzilla.samba.org/show_bug.cgi?id=3186 ------- Comment #1 from foner-rsync-bugzilla@media.mit.edu 2005-11-22 14:16 MST ------- Any ideas on this? It's been open 5 weeks and probably got overlooked... Tnx! -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are

https://bugzilla.samba.org/show_bug.cgi?id=3175 Summary: devices and --link-dest don't seem to work together Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I use rsync to download a directory from a remote daemon. This has worked well for years but has recently started to give problems. The rsync transfer is run by a program called dirvish that is run as a cron job. The log looks like this: ACTION: rsync -vrltH --delete --stats -D --numeric-ids --exclude-from=/nfs/scop5/data/msd/sifts-mirror/2016-06-28/exclude

I've noticed the 3.0.0pre versions sometimes hanging while doing a local copy (through dirvish). This time a had a binary with debugging symbols, so I could do gdb backtraces. This is the result: # ps -fe | grep rsync root 3712 3710 0 02:04 ? 00:00:03 rsync -vrltH --delete -pgo --stats -D --numeric-ids -x --exclude-from=/backup/0/oudeserver/laatste/exclude

> first <- data.frame(a=1:3, b=4:6) > second <- data.frame(b=7:9, c=10:12) > third <- merge(first, second, by="b", all=TRUE) > third b a c 1 4 1 NA 2 5 2 NA 3 6 3 NA 4 7 NA 10 5 8 NA 11 6 9 NA 12 It's easy to replace the Nas with whatever value you want. No, merge() does not work with more than two data sets at a time. Andy From: mtb954 at gmail.com

https://bugzilla.samba.org/show_bug.cgi?id=3175 ------- Additional Comments From foner-rsync-bugzilla@media.mit.edu 2005-10-17 04:36 ------- Created an attachment (id=1518) --> (https://bugzilla.samba.org/attachment.cgi?id=1518&action=view) Transcript of unsuccessful attempts I have other transcripts with me experimenting with all four possibilities of trailing or no trailing slash

Granzow, Doug (NCI) [granzowd@mail.nih.gov] writes: > Hmm... I have a filesystem that contains 3,098,119 files. That's > 3,098,119 * 56 bytes or 173,494,664 bytes (about 165 MB). Allowing > for the exponential resizing we end up with space for 4,096,000 > files * 56 bytes = 218 MB. But 'top' tells me the rsync running on > this filesystem is taking up 646 MB, about 3

usage appears to grow gradually, not exponentially. A rsync may take several hours to complete. (I have one running now that started over four hours ago. The filesystem contains 236 GB of data in 2.4 million files. It is currently taking up 1351MB of memory on the mirror server and 646M on the source server.) All filesystems are veritas filesystem, in case that is relevant. I saw someone on

https://bugzilla.samba.org/show_bug.cgi?id=3168 Summary: --min-size cores in 2.6.5 and is completely missing in 2.6.6 Product: rsync Version: 2.6.6 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi! It's me again with another --link-dest issue: I am using dirvish (www.dirvish.org) to create daily backup on disk images. dirvish is using rsync with --link-dest pointing to the last good image. This creates images with hardlinks to unmodified files. So far so good. Now I want to create a "current" filetree with hardlinks pointing to the last image. rsync -vaH --delete

I have recently built a new server using CentOS4. I've found one major oddity: time resolution is completely whacked. I'm not using an external time source nor am I relying on NTP for time resolution. For some reason, time on this server moves forward at a far more rapid rate. Right now, all my other systems show Sunday May 8, 3:19 pm. The CentOS server thinks its Monday May 9, 3:54

(I'm not sending this to dirvish@pegasus because I think that this message applies more to rsync's --link-dest option than to just dirvish.) I recently noticed a huge spike in dirvish network usage and traced it to files whose permissions had been changed. (with rsync v2.5.6) I understand and agree that a --link-dest copy of a source file cannot be hardlinked to, but couldn't a

I've been going nuts lately trying to get rid of an annoying echo problem that makes my asterisk server unusable when clients try to call me. Here's the breakdown of the issue - Hoping that someone can throw me a clue: My setup is as such: Single AMD Athon machine with X100P clone card and voip through multiple providers . * Inbound calls through the X100P that do not bridge to

I've got a problem for which the combination of -R and --link-dest doesn't seem to be quite enough---and I may have discovered a few small bugs as well; test cases are below. [And if someone has a scheme for doing this that doesn't involve rsync at all, but works okay, I'm all ears as well---I'm not the first with this problem.] Here's my problem: I unfortunately need to

https://bugzilla.samba.org/show_bug.cgi?id=3168 ------- Additional Comments From foner-rsync-bugzilla@media.mit.edu 2005-10-14 04:50 ------- Obtw, when this gets reinstated, it would be -really nice- if one or the other (but NOT BOTH) of --max-size or --min-size was an "OR EQUAL". Right now, if I'm trying to copy all files under one size to one place, and all files over one

Hi list, Now that I've got my Asterisk server to recognize my HFC-PCI card, I've run into some serious problems. The first thing I noticed was this message that would show up every five seconds on the CLI: Dec 27 15:46:42 WARNING[12484]: chan_zap.c:2512 pri_find_dchan: No D-channels available! Using Primary channel 3 as D-channel anyway! == Primary D-Channel on span 1 down

https://bugzilla.samba.org/show_bug.cgi?id=3277 Summary: [Feature req] "I couldn't do something you asked" warning Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi All, I am having a problem with Samba that seems to be a bug. I say this because I read the archives and they described a problem similar to mine and were told that it was a bug in older version of Samba and the latest version should have it fixed. I am running what is essentially a RH 7.3 on a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5 and am using the following

On Sun, 15 Jul 2007, Paolo Invernizzi wrote: > First, I'm not sure if deleting the ExecutionEngine is all I need to > clean-up... so I started with a minimal test just to check Is this llvm 2.0 or llvm svn head? Several minor memory leaks have been fixed since llvm 2.0. -Chris > int main( int argc, char **argv ){ > while( true ){ > Module *M = new

First, I'm not sure if deleting the ExecutionEngine is all I need to clean-up... so I started with a minimal test just to check int main( int argc, char **argv ){ while( true ){ Module *M = new Module("M"); Function *F = cast<Function>(M->getOrInsertFunction("F", Type::Int32Ty, (Type*)0)); BasicBlock *BB = new