<?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>thinking sysadmin &#187; corruption</title>
	<atom:link href="http://andyleonard.com/tag/corruption/feed/" rel="self" type="application/rss+xml" />
	<link>http://andyleonard.com</link>
	<description>qstat -u aleonard -s z</description>
	<lastBuildDate>Fri, 30 Jul 2010 17:47:40 +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>Linkage, 6/24/2008</title>
		<link>http://andyleonard.com/2008/06/24/linkage-6242008/</link>
		<comments>http://andyleonard.com/2008/06/24/linkage-6242008/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 23:19:37 +0000</pubDate>
		<dc:creator>Andy</dc:creator>
				<category><![CDATA[link dump]]></category>
		<category><![CDATA[aws]]></category>
		<category><![CDATA[corruption]]></category>
		<category><![CDATA[data integrity]]></category>
		<category><![CDATA[s3]]></category>

		<guid isPermaLink="false">http://andyleonard.com/?p=39</guid>
		<description><![CDATA[
S3 data corruption: &#8220;We&#8217;ve isolated this issue to a single load balancer that was brought into service at 10:55pm PDT on Friday, 6/20.  It was taken out of service at 11am PDT Sunday, 6/22.  While it was in service it handled a small fraction of Amazon S3&#8217;s total requests in the US.  [...]]]></description>
			<content:encoded><![CDATA[<ul>
<li><a href="http://developer.amazonwebservices.com/connect/message.jspa?messageID=93408#93408">S3 data corruption</a>: &#8220;We&#8217;ve isolated this issue to a single load balancer that was brought into service at 10:55pm PDT on Friday, 6/20.  It was taken out of service at 11am PDT Sunday, 6/22.  While it was in service it handled a small fraction of Amazon S3&#8217;s total requests in the US.  Intermittently, under load, it was corrupting single bytes in the byte stream.  When the requests reached Amazon S3, if the Content-MD5 header was specified, Amazon S3 returned an error indicating the object did not match the MD5 supplied.  When no MD5 is specified, we are unable to determine if transmission errors occurred, and Amazon S3 must assume that the object has been correctly transmitted.&#8221;  (Seen at <a href="http://www.daemonology.net/blog/2008-06-24-amazon-s3-data-corruption.html">Daemonic Dispatches</a>.)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://andyleonard.com/2008/06/24/linkage-6242008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
