<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for etbe - Russell Coker</title>
	<atom:link href="http://etbe.coker.com.au/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au</link>
	<description>Linux, politics, and other interesting things</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:45:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Reliability of RAID by Adam Skutt</title>
		<link>http://etbe.coker.com.au/2012/02/06/reliability-raid/comment-page-1/#comment-27217</link>
		<dc:creator>Adam Skutt</dc:creator>
		<pubDate>Wed, 08 Feb 2012 14:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=3151#comment-27217</guid>
		<description>I think you misunderstood me when I said &quot;considerable&quot;.  Systematic failure to honor warranties is the sort of thing that subjects you to class action lawsuits (which did happen to IBM), investigations by the US FTC (and similar agencies in other jurisdictions), and the like.  Past behavior by certain industries in this regard is why many jurisdictions have &quot;lemon laws&quot; and other explicit statues about warranties.  It&#039;s probably reasonable to assume a refurbished drive is of lower quality.  It&#039;s not the least bit reasonable to assume that means that QA is being entirely disregarded on the refurbished drives. Until recently, it was the standard policy of all the manufacturers to send you a brand new drive if your drive failed within a month (and it&#039;s still policy for enterprise drives, I believe).  That&#039;s not the policy of a company that&#039;s out to get you.

You&#039;re also fundamentally wrong about the economics in these situations.  Regardless of the quality of a product, all manufacturers must be prepared to accept returns for products sold at retail.  As such, the cost of bearing returned and failed products ends up being spread out over all the devices: if you get 1/1000 returned, and it costs X to refurbish it, then you add X/1000 to cost.  It may be a special case, but it&#039;s also not a special case companies can ignore.  Unless your product is really cheap (and hard drives are not really cheap), it makes no sense to throw away returns if you can resell them or offer them as warranty replacements, even if it costs you some money to do so.  As long as the cost is lower than the resale point, or the cost of a new device (for warranty replacements), it&#039;s economically sensible to do so.

Postage costs don&#039;t change the situation either.  They only have to pay postage one way (in the US, at least) and they ship the drives using the cheapest method available.  They negotiate pricing deals with the shipping companies.  Cost of shipping buying a drive from newegg to my house is $6.25 (guaranteed three day), so the manufacturers are doing as well, if not better, on warranty returns.  As a point of reference, Newegg sells refurbished drives for around $30-50 dollars each, while the cheapest new drives is about $70 (which is admittedly price distorted due to the flooding).  That&#039;s probably workable for the HDDs manufacturers.</description>
		<content:encoded><![CDATA[<p>I think you misunderstood me when I said &#8220;considerable&#8221;.  Systematic failure to honor warranties is the sort of thing that subjects you to class action lawsuits (which did happen to IBM), investigations by the US FTC (and similar agencies in other jurisdictions), and the like.  Past behavior by certain industries in this regard is why many jurisdictions have &#8220;lemon laws&#8221; and other explicit statues about warranties.  It&#8217;s probably reasonable to assume a refurbished drive is of lower quality.  It&#8217;s not the least bit reasonable to assume that means that QA is being entirely disregarded on the refurbished drives. Until recently, it was the standard policy of all the manufacturers to send you a brand new drive if your drive failed within a month (and it&#8217;s still policy for enterprise drives, I believe).  That&#8217;s not the policy of a company that&#8217;s out to get you.</p>
<p>You&#8217;re also fundamentally wrong about the economics in these situations.  Regardless of the quality of a product, all manufacturers must be prepared to accept returns for products sold at retail.  As such, the cost of bearing returned and failed products ends up being spread out over all the devices: if you get 1/1000 returned, and it costs X to refurbish it, then you add X/1000 to cost.  It may be a special case, but it&#8217;s also not a special case companies can ignore.  Unless your product is really cheap (and hard drives are not really cheap), it makes no sense to throw away returns if you can resell them or offer them as warranty replacements, even if it costs you some money to do so.  As long as the cost is lower than the resale point, or the cost of a new device (for warranty replacements), it&#8217;s economically sensible to do so.</p>
<p>Postage costs don&#8217;t change the situation either.  They only have to pay postage one way (in the US, at least) and they ship the drives using the cheapest method available.  They negotiate pricing deals with the shipping companies.  Cost of shipping buying a drive from newegg to my house is $6.25 (guaranteed three day), so the manufacturers are doing as well, if not better, on warranty returns.  As a point of reference, Newegg sells refurbished drives for around $30-50 dollars each, while the cheapest new drives is about $70 (which is admittedly price distorted due to the flooding).  That&#8217;s probably workable for the HDDs manufacturers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reliability of RAID by etbe</title>
		<link>http://etbe.coker.com.au/2012/02/06/reliability-raid/comment-page-1/#comment-27216</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Wed, 08 Feb 2012 13:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=3151#comment-27216</guid>
		<description>Legal action is really expensive. I recently got legal advice about a dispute, the lawyer owed me a favor so he wrote a letter for free but he advised me that if the other party to the dispute didn&#039;t just give in then I should forget about it. Amounts less than $10,000 aren&#039;t worth legal action due to the costs - which aren&#039;t always paid by the loser. The amount in question was equal to the cost of three SATA disks, fortunately the other guy just sent me a cheque and didn&#039;t dispute it.

When the amount of computer gear is worth legal action it still doesn&#039;t happen. Any time a company buys a $1,000,000 computer there are a variety of pressures on management not to escalate the dispute. My experience is that the Trade Practices Act is routinely violated by vendors of expensive gear and none of their customers complain.

One of my friends bought an IBM drive when they were going through a bad period. He had it replaced with refurbished disks three times before he requested a smaller disk (from a different series and therefore without the same defects).

The only reason for getting into a legal battle over a small amount of money is when there&#039;s a political battle and the money doesn&#039;t matter. EG the Linux users who sue for a refund of a MS license fee.

Really I can&#039;t understand why drive manufacturers don&#039;t just use returned drives as scrap metal and supply new disks. The costs of postage both ways would be a significant portion of the manufacture price of a new disk. So it should be better for them economically to just send a new disk and get the matter resolved. Posting drives back and forth three times is just bad for business. The economics of corporations is to not do special cases, they have an assembly line and run it as fast as possible. Refurbished gear is a special case and only makes sense if the gear is really expensive, and drives just aren&#039;t that expensive.</description>
		<content:encoded><![CDATA[<p>Legal action is really expensive. I recently got legal advice about a dispute, the lawyer owed me a favor so he wrote a letter for free but he advised me that if the other party to the dispute didn&#8217;t just give in then I should forget about it. Amounts less than $10,000 aren&#8217;t worth legal action due to the costs &#8211; which aren&#8217;t always paid by the loser. The amount in question was equal to the cost of three SATA disks, fortunately the other guy just sent me a cheque and didn&#8217;t dispute it.</p>
<p>When the amount of computer gear is worth legal action it still doesn&#8217;t happen. Any time a company buys a $1,000,000 computer there are a variety of pressures on management not to escalate the dispute. My experience is that the Trade Practices Act is routinely violated by vendors of expensive gear and none of their customers complain.</p>
<p>One of my friends bought an IBM drive when they were going through a bad period. He had it replaced with refurbished disks three times before he requested a smaller disk (from a different series and therefore without the same defects).</p>
<p>The only reason for getting into a legal battle over a small amount of money is when there&#8217;s a political battle and the money doesn&#8217;t matter. EG the Linux users who sue for a refund of a MS license fee.</p>
<p>Really I can&#8217;t understand why drive manufacturers don&#8217;t just use returned drives as scrap metal and supply new disks. The costs of postage both ways would be a significant portion of the manufacture price of a new disk. So it should be better for them economically to just send a new disk and get the matter resolved. Posting drives back and forth three times is just bad for business. The economics of corporations is to not do special cases, they have an assembly line and run it as fast as possible. Refurbished gear is a special case and only makes sense if the gear is really expensive, and drives just aren&#8217;t that expensive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reliability of RAID by Adam Skutt</title>
		<link>http://etbe.coker.com.au/2012/02/06/reliability-raid/comment-page-1/#comment-27215</link>
		<dc:creator>Adam Skutt</dc:creator>
		<pubDate>Wed, 08 Feb 2012 12:58:37 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=3151#comment-27215</guid>
		<description>I&#039;m not sure why people think it&#039;s trivial to just make a hard drive that last less longer with any sort of regularity or consistency, or that it&#039;s trivial to figure out when a particular drive will fail.  Even if the QA on failed drives is somehow lower, it&#039;s not &lt;i&gt;years&lt;/i&gt; lower.  Manufacturers also have a huge incentive to properly refurbish their drives: repeated failures would open them up to considerable legal action.  Heck, sufficient widespread failure of the original equipment is enough legal action, you don&#039;t want to be routinely selling product that fails within the warranty period.  You definitely don&#039;t want to replace a failed product with something else that fails in the warranty period.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure why people think it&#8217;s trivial to just make a hard drive that last less longer with any sort of regularity or consistency, or that it&#8217;s trivial to figure out when a particular drive will fail.  Even if the QA on failed drives is somehow lower, it&#8217;s not <i>years</i> lower.  Manufacturers also have a huge incentive to properly refurbish their drives: repeated failures would open them up to considerable legal action.  Heck, sufficient widespread failure of the original equipment is enough legal action, you don&#8217;t want to be routinely selling product that fails within the warranty period.  You definitely don&#8217;t want to replace a failed product with something else that fails in the warranty period.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 5 Principles of Backup Software by Brendan</title>
		<link>http://etbe.coker.com.au/2012/02/07/5-principles-backup/comment-page-1/#comment-27214</link>
		<dc:creator>Brendan</dc:creator>
		<pubDate>Wed, 08 Feb 2012 10:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=3154#comment-27214</guid>
		<description>PS: on Android an app&#039;s data is private to that app (including if it&#039;s connected for debugging).  The app must, itself, have a function for exporting it to a public area on the SD card and a second function for importing them again.  

Maybe what needed to be backed up was too tedious for them to be bothered coding it in Java?</description>
		<content:encoded><![CDATA[<p>PS: on Android an app&#8217;s data is private to that app (including if it&#8217;s connected for debugging).  The app must, itself, have a function for exporting it to a public area on the SD card and a second function for importing them again.  </p>
<p>Maybe what needed to be backed up was too tedious for them to be bothered coding it in Java?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 5 Principles of Backup Software by Brendan</title>
		<link>http://etbe.coker.com.au/2012/02/07/5-principles-backup/comment-page-1/#comment-27213</link>
		<dc:creator>Brendan</dc:creator>
		<pubDate>Wed, 08 Feb 2012 10:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=3154#comment-27213</guid>
		<description>I once tried to recover a tar file, but was told (by tar) that the format was too old.  The tar was made in 1991 ish, and I think I was trying to recover it 10-12 years or so later.    I don&#039;t know if the archive was corrupted.</description>
		<content:encoded><![CDATA[<p>I once tried to recover a tar file, but was told (by tar) that the format was too old.  The tar was made in 1991 ish, and I think I was trying to recover it 10-12 years or so later.    I don&#8217;t know if the archive was corrupted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reliability of RAID by Nick J</title>
		<link>http://etbe.coker.com.au/2012/02/06/reliability-raid/comment-page-1/#comment-27208</link>
		<dc:creator>Nick J</dc:creator>
		<pubDate>Wed, 08 Feb 2012 04:03:07 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=3151#comment-27208</guid>
		<description>&gt; I know of one manufacturer that had a routine practice of refurbishing
&gt; drives that were returned under warranty and then giving them to other
&gt; people.

IBM used to do it, before they sold the business to Hitachi (returned disks had a &quot;certified repaired part&quot; sticker on them) - I asked about this and they said by law they had to put the sticker on (heaven forbid they just sent out new disk). Seagate still does it - I have 2 disks here that have a green disk sticker with &quot;Certified Repaired HDD&quot; on them, and then one of them died just out of the  replacement warranty period.

I think the better question is: which disk manufacturers do not send out repaired disks? Are Western Digital or Samsung any better?

&gt; Nick, I have seen email in the event of actual MD RAID-1 failure.

Doh! Just tested, and this was my fault. I changed ISPs and the outgoing smarthost was still set to the old ISP&#039;s, so outgoing mail was backlogged.

So yes, you should in fact get a mail with a subject like so: &quot;DegradedArray event on /dev/md0&quot;, and mailing can be tested with: sudo mdadm --monitor --test --oneshot /dev/md0

&gt; I presume they&#039;re not sending people back their original drive

No, they&#039;re not - they make a big song and dance about how you won&#039;t get back the same drive, and for a seagate one, I just checked the replacement drive&#039;s details against the original&#039;s, and it&#039;s not the same serial number, and not even the same model number (it&#039;s a similar model number, and the disk has the same interface and capacity). Looks like the returned ones go into a big pool and are reused as spare parts for repaired disks if possible.

&gt; If you don&#039;t trust their ability to QA a failed drive then there&#039;s
&gt; no rational reason to trust their ability to QA a brand new drive, either

But they might have lower standards, and it&#039;s probably in their financial interest to do so. If the warranty on a new drive is 5 years, and then you have drive fail after 4 years (which has happened to me), then they have no incentive to return you a repaired drive that will last more than 1 year, since beyond that period you&#039;re out of warranty. Furthermore, even if the replacement subsequently fails in the warranty period, since the manufacturer is sending out repaired parts, and you&#039;ll know this after the first replacement, your incentive to get it replaced is reduced, since you&#039;ll suspect that the 2nd replacement is more likely to fail too. Because of this, I&#039;ve come to feel the warranties on drives are relatively useless. It&#039;d be different if I knew at the time of purchase that I&#039;d get a new drive in the event of a failure.</description>
		<content:encoded><![CDATA[<p>&gt; I know of one manufacturer that had a routine practice of refurbishing<br />
&gt; drives that were returned under warranty and then giving them to other<br />
&gt; people.</p>
<p>IBM used to do it, before they sold the business to Hitachi (returned disks had a &#8220;certified repaired part&#8221; sticker on them) &#8211; I asked about this and they said by law they had to put the sticker on (heaven forbid they just sent out new disk). Seagate still does it &#8211; I have 2 disks here that have a green disk sticker with &#8220;Certified Repaired HDD&#8221; on them, and then one of them died just out of the  replacement warranty period.</p>
<p>I think the better question is: which disk manufacturers do not send out repaired disks? Are Western Digital or Samsung any better?</p>
<p>&gt; Nick, I have seen email in the event of actual MD RAID-1 failure.</p>
<p>Doh! Just tested, and this was my fault. I changed ISPs and the outgoing smarthost was still set to the old ISP&#8217;s, so outgoing mail was backlogged.</p>
<p>So yes, you should in fact get a mail with a subject like so: &#8220;DegradedArray event on /dev/md0&#8243;, and mailing can be tested with: sudo mdadm &#8211;monitor &#8211;test &#8211;oneshot /dev/md0</p>
<p>&gt; I presume they&#8217;re not sending people back their original drive</p>
<p>No, they&#8217;re not &#8211; they make a big song and dance about how you won&#8217;t get back the same drive, and for a seagate one, I just checked the replacement drive&#8217;s details against the original&#8217;s, and it&#8217;s not the same serial number, and not even the same model number (it&#8217;s a similar model number, and the disk has the same interface and capacity). Looks like the returned ones go into a big pool and are reused as spare parts for repaired disks if possible.</p>
<p>&gt; If you don&#8217;t trust their ability to QA a failed drive then there&#8217;s<br />
&gt; no rational reason to trust their ability to QA a brand new drive, either</p>
<p>But they might have lower standards, and it&#8217;s probably in their financial interest to do so. If the warranty on a new drive is 5 years, and then you have drive fail after 4 years (which has happened to me), then they have no incentive to return you a repaired drive that will last more than 1 year, since beyond that period you&#8217;re out of warranty. Furthermore, even if the replacement subsequently fails in the warranty period, since the manufacturer is sending out repaired parts, and you&#8217;ll know this after the first replacement, your incentive to get it replaced is reduced, since you&#8217;ll suspect that the 2nd replacement is more likely to fail too. Because of this, I&#8217;ve come to feel the warranties on drives are relatively useless. It&#8217;d be different if I knew at the time of purchase that I&#8217;d get a new drive in the event of a failure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

