rsync: pack_smb_acl: sys_acl_init(): Cannot allocate memory
Before I call this a bug, I figured I'd ask -- what's the + 3 for in
calc_sacl_entries?
static int calc_sacl_entries(const rsync_acl *racl)
{
/* A System ACL always gets user/group/other permission entries. */
return racl-names.count
#ifdef ACLS_NEED_MASK
+ 4;
#else
+ (racl-mask_obj != NO_ENTRY) + 3; What's this for?
#endif
}
On Mac OS X, a file with the system limit of 128 ACEs will consistently run
into the error noted in the subject. calc_sacl_entries is returning 131 for
such a file, and acl_init() returns ENOMEM as a result. If I remove the + 3,
everything is peachy -- all the ACEs are copied and I don't see any harm. Is
there an unforeseen consequence to removing the +3?
This script reliably reproduces the error:
##
#!/bin/sh
rsync=/usr/local/bin/rsync
src=`mktemp -d /tmp/src.XX`
tgt=`mktemp -d /tmp/tgt.XX`
echo $tgt/test
file=$src/test
touch $file
x=0
limit=128
while [ $x -lt $limit ] ; do
chmod +a# $x $USER allow write,writeattr,writeextattr $file
x=$(($x + 1))
done
$rsync -vaAX $src/ $tgt/
rm -rf $src $tgt
##
Thanks,
Mike
--
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
Re: read errors mapping filename: Cannot allocate memory (12)
On Mon, Jan 11, 2010 at 3:12 AM, Matthias Adler rs...@cronic.de wrote: rsync: read errors mapping filename: Cannot allocate memory (12) The read errors mapping error is output when the read() calls for a file returned an error to the sender. The errno (12) is what the OS indicated for the failure. Having a read() return Cannot allocate memory makes it seem like something is very wrong in the OS -- that's not a typical error that read() should return. ..wayne.. -- 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
read errors mapping filename: Cannot allocate memory (12)
I use rsync to copy files from various Windows servers to a backup server running linux (OpenSUSE 11.2, filesystem ext3). The files that are to be copied reside in CIFS shares which are mounted on the backup server. This is the command I run: rsync -rltv --out-format=./%n%L --delete --exclude-from=excludes.txt --link-dest=/backup/local/20100110/server1/backup$ '/backup/server1/backup$/' '/backup/local/20100111/server1/backup$' When copying a rather large file (34 GB) I get the following error: rsync: read errors mapping filename: Cannot allocate memory (12) WARNING: filename failed verification -- update discarded (will try again). rsync: read errors mapping filename: Cannot allocate memory (12) ERROR: filename failed verification -- update discarded. It is the only file I have problems with. I upgraded from rsync 2.6.4 to 3.0.6 and increased the memory on the machine from 1 GB to 1.5 GB, but the problem remains. -- 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
Rsync / Cygwin : Cannot Allocate Memory
Hi, I'm running the latest cygwin, with rsync 2.6.6 protocol 26. My command is: c:\cygwin\bin\rsync -vrtz --delete /cygdrive/e [EMAIL PROTECTED] etc I get the following error when trying to rsync 500,000 files: rsync: fork failed in do_recv: Cannot allocate memory (12) rsync error: error in IPC code (code 14) at main.c(550) rsync: connection unexpectedly closed (4 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.6/io.c(434) Of course, this doesn't happen with a smaller fileset. I'd prefer to not have to break up the transfer, as the programmers tend to just create directories wherever they please and don't tell me when they do, then complain that their stuff isn't backed up (been there). But I'm kinda lost - I found a post that says each file uses 100 bytes, the reference poster was trying to archive 5,000,000 files - which is far more than I am. According to that post, my memory requirements would only be 50,000,000 bytes. 50MB. Even if that doubled since the post, it'd still only be 100MB. The odd thing is, It WAS working with rsync 2.5.1-dev (from an rsync_minimal archive I found on the web) - except that one was crashing on a 2GB file (damn outlook pst files), but I was getting past the filelist part. I tried upping the memory for cygwin, because the new version has a limit of 384MB, and I thought MAYBE the dll I grabbed had no limit - but upping to 1024MB didn't work. This is on a Win2k box. Any suggestions? Thanks Rick -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync / Cygwin : Cannot Allocate Memory
On Fri, Mar 24, 2006 at 08:20:18AM -0600, Rick Romero wrote: rsync: fork failed in do_recv: Cannot allocate memory (12) This error is happening on the receiving side, and you seem to have only mentioned the OS and memory for the sending system (I assume -- you didn't explicitly say). Is the receiving system also running cygwin? What is its version rsync? ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync / Cygwin : Cannot Allocate Memory
Wayne Davison wrote: On Fri, Mar 24, 2006 at 08:20:18AM -0600, Rick Romero wrote: rsync: fork failed in do_recv: Cannot allocate memory (12) This error is happening on the receiving side, and you seem to have only mentioned the OS and memory for the sending system (I assume -- you didn't explicitly say). Is the receiving system also running cygwin? What is its version rsync? ..wayne.. Ahhh The receiving side is a fresh install of Debian, kernel 2.6.8-2 with a whopping 256MB of Ram. I have 2Mb 'free', no swap (What the heck did I do there? Watch my confidence start droping drastically :P ) and 5 rsync processes eating about 35Mb each.. The receiving system is running rsync 2.6.4 protocol v29. Ok, so I'll throw another 256Mb in there asap - I still don't know why just changing the sending side's version of rsync would cause the receiving side to run out of memory.. Thanks Rick -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync / Cygwin : Cannot Allocate Memory
Rick Romero wrote: Wayne Davison wrote: On Fri, Mar 24, 2006 at 08:20:18AM -0600, Rick Romero wrote: rsync: fork failed in do_recv: Cannot allocate memory (12) This error is happening on the receiving side, and you seem to have only mentioned the OS and memory for the sending system (I assume -- you didn't explicitly say). Is the receiving system also running cygwin? What is its version rsync? ..wayne.. Ahhh The receiving side is a fresh install of Debian, kernel 2.6.8-2 with a whopping 256MB of Ram. I have 2Mb 'free', no swap (What the heck did I do there? Watch my confidence start droping drastically :P ) and 5 rsync processes eating about 35Mb each.. The receiving system is running rsync 2.6.4 protocol v29. Ok, so I'll throw another 256Mb in there asap - I still don't know why just changing the sending side's version of rsync would cause the receiving side to run out of memory.. Adding more memory to the receiving side seems to have solved that issue. Now if I could only go back a day and find my own thread in the archives.. no wait, that wouldn't work.. damnit Thanks :) Rick -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Cannot Allocate Memory
On Tue, 7 Jun 2005, Max Kipness [EMAIL PROTECTED] wrote:
I've just upgraded to 2.6.5.
On a new set of servers I'm trying to sync I seem to be running into a log
of memory allocation errors.
With some of the servers, I start the rsync session, and it counts so many
files and then stops. At that point I'm unable to control-c out of the
process. From another session I can't issue a kill command either...very
strange.
A control-C might not always work, but a kill -9 {PID} should. If it
doesn't, there may be some OS-related problem in your brand-new servers.
On other servers, the first few files/directories issue a 'cannot allocate
memory', but strangly enough, it continues on.
If that's an actual quote of the error message, it's not from rsync.
Rsync uses ERROR: out of memory in {NameOfRoutine}, and then exits.
Does this simply mean that the 256mb memory isn't sufficient? I am trying
to sync a very large folder structure.
At an average of 100 bytes per file, you could do 1 million files in
100 MB, so unless you have a real whopper, 256 MB should be just fine
especially if you also have some swap space.
Is there anyway around this using tmp disk space or something until I can
get more memory?
Using swap should effectively use temp disk space.
What are your ulimit values? If you are running as root it shouldn't matter,
but small memory limits might trigger a problem.
But the overall symptoms imply a deeper problem, IMO.
John
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Cannot Allocate Memory
Hello - I've just upgraded to 2.6.5. On a new set of servers I'm trying to sync I seem to be running into a log of memory allocation errors. With some of the servers, I start the rsync session, and it counts so many files and then stops. At that point I'm unable to control-c out of the process. From another session I can't issue a kill command either...very strange. On other servers, the first few files/directories issue a 'cannot allocate memory', but strangly enough, it continues on. Does this simply mean that the 256mb memory isn't sufficient? I am trying to sync a very large folder structure. Is there anyway around this using tmp disk space or something until I can get more memory? Thanks, Max -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
