My Oracle Support Banner

Understanding Why "hdfs fsck / -move" to Move Corrupt Blocks to the "lost+found" Directory Fails (Doc ID 2111298.1)

Last updated on DECEMBER 24, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 and later
Linux x86-64


The goal is to understand why "hdfs fsck / -move"  or "hdfs fsck <PATH_TO_BLOCK> -move" to move corrupt blocks to the "lost+found" directory fails.

The problem symptom is that the "-move" option fails as below:



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Background to the failure:
 Why would moving the corrupt blocks to lost+found with "hdfs fsck / -move" fail?
 Is there a way to save these blocks?
 In the case of corrupt blocks without missing files, should "fsck -move" work?
 What does "fsck -move" do?
 Why would blocks become corrupt?
 Why would blocks have a replication factor of 1?
 Can the replication factor be increased to 3?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.