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

Last updated on FEBRUARY 29, 2016

Applies to:

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

Goal

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:

 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms