<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>My Waste of Bandwidth &#187; rsync</title>
	<atom:link href="http://www.mywasteofbandwidth.com/tag/rsync/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mywasteofbandwidth.com</link>
	<description>A seldomly updated look into my geeky happenings</description>
	<lastBuildDate>Sat, 13 Feb 2010 19:35:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Rsync Memory Allocation Error</title>
		<link>http://www.mywasteofbandwidth.com/2009/08/02/rsync-memory-allocation-error/</link>
		<comments>http://www.mywasteofbandwidth.com/2009/08/02/rsync-memory-allocation-error/#comments</comments>
		<pubDate>Sun, 02 Aug 2009 15:40:04 +0000</pubDate>
		<dc:creator>Joel</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[memory allocation error]]></category>
		<category><![CDATA[rsync]]></category>

		<guid isPermaLink="false">http://www.mywasteofbandwidth.com/?p=136</guid>
		<description><![CDATA[Recently, I&#8217;ve been working to improve our data backups  at home (stay tuned for a future article).  Part of my backup strategy involves syncing our main data repository with a drive in another system.  This is done using rsync, one of my favorite Linux utilities.
I&#8217;ve used rsync successfully for many years, but [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, I&#8217;ve been working to improve our data backups  at home (stay tuned for a future article).  Part of my backup strategy involves syncing our main data repository with a drive in another system.  This is done using <a href="http://rsync.samba.org/">rsync</a>, one of my favorite Linux utilities.</p>
<p>I&#8217;ve used rsync successfully for many years, but recently I started experiencing a &#8220;memory allocation error(12)&#8221; while syncing data between my Linux system and a Windows Vista system, with the Linux system as the source.  Using the Vista system as the source did not result in this error.</p>
<p>I searched all over the web looking for a resolution, but information was minimal and the best answer I found was to try <a href="http://rsync.samba.org/FAQ.html#4">splitting the  rsync command into smaller chunks</a>.  Unfortunately, that didn&#8217;t work.</p>
<p>I noticed when this error occurred, the shares on the Vista system became inaccessible with a reboot of Windows the only workaround.  This led me to investigate the event logs on the Vista machine.  Lo and behold, there in the system log I see this:</p>
<p><span style="color: #0000ff;">&#8220;The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.&#8221;</span></p>
<p>A quick online search for this error message indicated it was caused by a problem with SMBv2, which is the default version of SMB used  in Windows Vista.  However, you can force Vista to use SMBv1 by making a simple registry change.</p>
<p><strong>HKEY_LOCAL_MACHINE</strong> -&gt;<strong>SYSTEM</strong> -&gt;<strong>CurrentControlSet</strong> -&gt;<strong>Services</strong> -&gt;<strong>LanmanServer</strong> -&gt; <strong>Parameters</strong> and create a DWORD called <strong>SMB2</strong> with a value of <strong>0</strong>.</p>
<p>With the value set in the registry and a quick reboot of Vista, rsync was able to complete successfully.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mywasteofbandwidth.com/2009/08/02/rsync-memory-allocation-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
