Understanding Why "hdfs fsck / -move" to Move Corrupt Blocks to the "lost+found" Directory Fails
Last updated on FEBRUARY 29, 2016
Applies to:Big Data Appliance Integrated Software - Version 4.2.0 and later
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: