<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question CDH3: disk failure, datanode doesn't start even after disk replacement in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH3-disk-failure-datanode-doesn-t-start-even-after-disk/m-p/8808#M1581</link>
    <description>&lt;DIV&gt;&lt;DIV&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;in our &lt;STRONG&gt;CDH3&lt;/STRONG&gt; cluster (hadoop-0.20.2, yes, it's pretty old &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; ) we had a disk failure on one node and thereby the datanode went down.&lt;BR /&gt;After replacing the disk and setting up directories/permissions, starting the datanode still fails with this error:&lt;BR /&gt;&lt;BR /&gt;2014-04-15 16:14:43,165 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: org.apache.hadoop.util.DiskChecker$DiskErrorException: Too many failed volumes - current valid volumes: 5, volumes configured: 6, volumes failed: 1, volume failures tolerated: 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.FSDataset.&amp;lt;init&amp;gt;(FSDataset.java:1025)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:416)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.&amp;lt;init&amp;gt;(DataNode.java:303)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:1643)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:1583)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:1601)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:1727)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:1744)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;How to tell the datanode that the disk has been replaced, or how to "enable" the replaced disk ?!?!&lt;BR /&gt;I don't want to configure a tolerated disk failure of 1 to be able to start the datanode &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;P&gt;br, Gerd&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 08:57:29 GMT</pubDate>
    <dc:creator>geko</dc:creator>
    <dc:date>2022-09-16T08:57:29Z</dc:date>
    <item>
      <title>CDH3: disk failure, datanode doesn't start even after disk replacement</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH3-disk-failure-datanode-doesn-t-start-even-after-disk/m-p/8808#M1581</link>
      <description>&lt;DIV&gt;&lt;DIV&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;in our &lt;STRONG&gt;CDH3&lt;/STRONG&gt; cluster (hadoop-0.20.2, yes, it's pretty old &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; ) we had a disk failure on one node and thereby the datanode went down.&lt;BR /&gt;After replacing the disk and setting up directories/permissions, starting the datanode still fails with this error:&lt;BR /&gt;&lt;BR /&gt;2014-04-15 16:14:43,165 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: org.apache.hadoop.util.DiskChecker$DiskErrorException: Too many failed volumes - current valid volumes: 5, volumes configured: 6, volumes failed: 1, volume failures tolerated: 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.FSDataset.&amp;lt;init&amp;gt;(FSDataset.java:1025)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:416)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.&amp;lt;init&amp;gt;(DataNode.java:303)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:1643)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:1583)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:1601)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:1727)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; at org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:1744)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;How to tell the datanode that the disk has been replaced, or how to "enable" the replaced disk ?!?!&lt;BR /&gt;I don't want to configure a tolerated disk failure of 1 to be able to start the datanode &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;P&gt;br, Gerd&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 08:57:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH3-disk-failure-datanode-doesn-t-start-even-after-disk/m-p/8808#M1581</guid>
      <dc:creator>geko</dc:creator>
      <dc:date>2022-09-16T08:57:29Z</dc:date>
    </item>
    <item>
      <title>Re: CDH3: disk failure, datanode doesn't start even after disk replacement</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH3-disk-failure-datanode-doesn-t-start-even-after-disk/m-p/8836#M1582</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;issue has been solved. Problem was that there was a mismatch between directory permissions and ownership (owner was 700, not the permissions, stupid thing &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; ).&lt;/P&gt;&lt;P&gt;Nevertheless the error message is somehow misleading and it would preferrably print that the user/permissions are incorrect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gerd&lt;/P&gt;</description>
      <pubDate>Tue, 15 Apr 2014 19:17:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH3-disk-failure-datanode-doesn-t-start-even-after-disk/m-p/8836#M1582</guid>
      <dc:creator>geko</dc:creator>
      <dc:date>2014-04-15T19:17:23Z</dc:date>
    </item>
  </channel>
</rss>

