search for: util2

Sorry to keep replying to myself: > Because this is a Time Machine backup, and there were 66 snapshots of a > 1 TB disk consuming about 1.5 TB, there were a *lot* of hard links. Many > of directories rather than individual files, so it's a little Err, whoops? No, I was tired and confused. They are not hard links to directories, that would screw up the universe. Still, lots of hard

.../acls on 1.5 TB of data (not copying the data), and then it just died in the middle with: .L....og.... 2015-03-11-094807/platinum-bar2/usr/local/mysql -> mysql-5.6.21-osx 10.8-x86_64 ERROR: out of memory in expand_item_list [sender] rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2] rsync: [sender] write error: Broken pipe (32) It was invoked as rsync -iaHJAX platinum-barzoom/Backups.backupdb/pb3/ platinum-barratry/x/Backups.backupdb/pb3/ I suspect the situation will be different the next time around, and I'm also not really inclined to try to wai...

...[1] offset=131072 len=131072 sum1=3d66e7f7 [omitted] chunk[6550] offset=858521600 len=131072 sum1=d70deab6 chunk[6551] offset=858652672 len=131072 sum1=657e34df send_files(0, /bay3/b.tc) count=33554432 n=131072 rem=0 ERROR: out of memory in receive_sums [sender] [sender] _exit_cleanup(code=22, file=util2.c, line=105): entered rsync error: error allocating core memory buffers (code 22) at util2.c(105) [sender=3.1.3] This is getting called: 92 if (!(s->sums = new_array(struct sum_buf, s->count))) 93 out_of_memory("receive_sums"); And the size of a...

...eel.aron at gmail.com>>: > >> Hi Roland, > >> I just upgrade both the client and host to 3.1.1 and seem to >> memory related issues now: > >> ERROR: out of memory in make_file [sender] rsync error: error >> allocating core memory buffers (code 22) at util2.c(102) >> [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c, >> line=102): about to call exit(22) [Receiver] >> _exit_cleanup(code=22, file=io.c, line=1633): about to call >> exit(22) > > > - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._...

...d, with enabled checksums. Whith one of the shares I get the error (in syslog): --------------------------------------------------------------------- robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender] robbe rsyncd[2183]: rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2dev] robbe rsyncd[9821]: connect from elefant.control.local (192.168.1.200) robbe rsyncd[9821]: rsync on . from backuppc at elefant.control.local (192.168.1.200) --------------------------------------------------------------------- I read that the memory overflow comes from bul...

Hi, I am experiencing segfaults when transferring files via rsync though sudo. Setup: - Backupserver initiates the rsync command with --delete -vvv --no-inc-recursive --numeric-ids --delete-excluded --relative --rsync-path=/home/backupuser/rsync-wrapper.sh - rsync-wrapper.sh (on the client) contains /usr/bin/sudo /usr/bin/rsync "$@"; - user "backupuser" has sudo access to the

...-n, in this case it is just for testing reasons included. In case the source is located on an Ext4 file system we run into the following error message after about 26 million files copied: ERROR: out of memory in hashtable_node [sender] rsync error: error allocating core memory buffers (code 22) at util2.c(102) [sender=3.1.0] In case the source is located on an XFS file system the above command copies all files without error. Both of the file systems hold the same data as the one is the backup copy of the other. The behaviour appears as well when we use rsync via an rsync server and not via SSH and...

...>>: > >>> Hi Roland, > >>> I just upgrade both the client and host to 3.1.1 and seem to >>> memory related issues now: > >>> ERROR: out of memory in make_file [sender] rsync error: error >>> allocating core memory buffers (code 22) at util2.c(102) >>> [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c, >>> line=102): about to call exit(22) [Receiver] >>> _exit_cleanup(code=22, file=io.c, line=1633): about to call >>> exit(22) > > > > > -- Please use reply-all for most...

...uot;rsync.h" in popt/findme.c > > > >Structurally, this seems very odd. I thought popt was a generic argument > handler, > >which should not need to #include details of the application that is using > it. > > I thought so too, but it is now pulling in things from util2 and other > areas > needing rsync.h and ifuncs.h. > I still have not managed to get it to link correctly on ia64 and am > seriously considering giving up. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync...

...k this is just missing #include "rsync.h" in popt/findme.c > >Structurally, this seems very odd. I thought popt was a generic argument handler, >which should not need to #include details of the application that is using it. I thought so too, but it is now pulling in things from util2 and other areas needing rsync.h and ifuncs.h. I still have not managed to get it to link correctly on ia64 and am seriously considering giving up.

...k this is just missing #include "rsync.h" in popt/findme.c > >Structurally, this seems very odd. I thought popt was a generic argument handler, >which should not need to #include details of the application that is using it. I thought so too, but it is now pulling in things from util2 and other areas needing rsync.h and ifuncs.h. I still have not managed to get it to link correctly on ia64 and am seriously considering giving up. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20250115/63af53a...

...config.h.in:/* Define to 1 if you have the `usleep' function. */ configure.ac: initgroups utimensat posix_fallocate attropen setvbuf usleep) configure.sh: initgroups utimensat posix_fallocate attropen setvbuf usleep OLDNEWS: - Use usleep() for our msleep() function if it is available. util2.c: usleep(t*1000); for my curiosity, that went into rsync @2014, which is not too long ago: https://git.samba.org/rsync.git/?p=rsync.git;a=commit;h=5546dab32970955e77ef7a5886bcd8fb765a25bf http://man7.org/linux/man-pages/man2/nanosleep.2.html is telling: Compared to sleep(3) and uslee...

...> > >> Hi Roland, > > > >> I just upgrade both the client and host to 3.1.1 and seem to > >> memory related issues now: > > > >> ERROR: out of memory in make_file [sender] rsync error: error > >> allocating core memory buffers (code 22) at util2.c(102) > >> [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c, > >> line=102): about to call exit(22) [Receiver] > >> _exit_cleanup(code=22, file=io.c, line=1633): about to call > >> exit(22) > > > > > > > > - -- > ~*-,._.,-*~...

Hi, I wonder what is a better way to organize a lot of R source files. I have a lot of utility functions written and store them in several source files (e.g util1.R, util2.R,..utilN.R). I also have a master file in which the source command is used to load all the util.R files. When I need to use the utility functions in a new project, I create a new R file (e.g main.R) in which I "source" the master file. The problem with this approach is that anytime a si...

...ail.com>: >> >> Hi Roland, >> >> I just upgrade both the client and host to 3.1.1 and seem to memory >> related issues now: >> >> ERROR: out of memory in make_file [sender] >> rsync error: error allocating core memory buffers (code 22) at >> util2.c(102) [sender=3.1.1] >> [sender] _exit_cleanup(code=22, file=util2.c, line=102): about to call >> exit(22) >> [Receiver] _exit_cleanup(code=22, file=io.c, line=1633): about to call >> exit(22) >> >> ---------------------------------------------------------------...

...t; Hi Roland, > > > >>> I just upgrade both the client and host to 3.1.1 and seem to > >>> memory related issues now: > > > >>> ERROR: out of memory in make_file [sender] rsync error: error > >>> allocating core memory buffers (code 22) at util2.c(102) > >>> [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c, > >>> line=102): about to call exit(22) [Receiver] > >>> _exit_cleanup(code=22, file=io.c, line=1633): about to call > >>> exit(22) > > > > > > > > >...

...gmail.com>: > > > > Hi Roland, > > > > I just upgrade both the client and host to 3.1.1 and seem to memory > > related issues now: > > > > ERROR: out of memory in make_file [sender] rsync error: error > > allocating core memory buffers (code 22) at util2.c(102) > > [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c, > > line=102): about to call exit(22) [Receiver] _exit_cleanup(code=22, > > file=io.c, line=1633): about to call exit(22) > > > ------------------------------------------------------------------------...

...gt; >> >>> I just upgrade both the client and host to 3.1.1 and seem to >> >>> memory related issues now: >> > >> >>> ERROR: out of memory in make_file [sender] rsync error: error >> >>> allocating core memory buffers (code 22) at util2.c(102) >> >>> [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c, >> >>> line=102): about to call exit(22) [Receiver] >> >>> _exit_cleanup(code=22, file=io.c, line=1633): about to call >> >>> exit(22) >> > >> > &...

...h one of the shares I get the error (in > syslog): > --------------------------------------------------------------------- > > robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender] > robbe rsyncd[2183]: rsync error: error allocating core memory > buffers (code 22) at util2.c(106) [sender=3.1.2dev] robbe > rsyncd[9821]: connect from elefant.control.local (192.168.1.200) > robbe rsyncd[9821]: rsync on . from backuppc at elefant.control.local > (192.168.1.200) > --------------------------------------------------------------------- > > I read that t...

...v6, batchfiles, inplace, append, ACLs, no xattrs, iconv, no symtimes, no prealloc I'm hoping that by using 64-bit inums, I will be able to avoid this error that I'm getting: ERROR: out of memory in flist_expand [sender] rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2] rsync: [sender] write error: Broken pipe (32) I've gotten around this by sub-dividing the rsync into smaller chunks but would like to avoid this if possible. Thanks in advance, Tom -- Tom Combs Systems Administrator Information Technology Services Florida State Univer...