apache/hadoop · error · IllegalArgumentException
Pathname from is not a valid DFS filename.
Error message
Pathname from is not a valid DFS filename.
What it means
Error "Pathname from is not a valid DFS filename." thrown in apache/hadoop.
Source
Thrown at hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DistributedFileSystem.java:265
* @return object of DFSHedgedReadMetrics
*/
public DFSHedgedReadMetrics getHedgedReadMetrics() {
return dfs.getHedgedReadMetrics();
}
/**
* Checks that the passed URI belongs to this filesystem and returns
* just the path component. Expects a URI with an absolute path.
*
* @param file URI with absolute path
* @return path component of {file}
* @throws IllegalArgumentException if URI does not belong to this DFS
*/
String getPathName(Path file) {
checkPath(file);
String result = file.toUri().getPath();
if (!DFSUtilClient.isValidName(result)) {
throw new IllegalArgumentException("Pathname " + result + " from " +
file+" is not a valid DFS filename.");
}
return result;
}
@Override
public BlockLocation[] getFileBlockLocations(FileStatus file, long start,
long len) throws IOException {
if (file == null) {
return null;
}
return getFileBlockLocations(file.getPath(), start, len);
}
/**
* The returned BlockLocation will have different formats for replicated
* and erasure coded file.
* Please refer toView on GitHub (pinned to 2add963021)
Solutions
- Ensure the 'from' pathname is a valid DFS filename (absolute path, no scheme mismatch).
- Check for typos or unsupported characters in the source path before rename.
When it happens
Trigger: A rename or similar operation is given a source pathname that is not a valid DFS filename, so the operation is rejected client-side.
Common situations: See trigger scenarios.
AI-assisted analysis of apache/hadoop@2add963021 (2026-08-22).
Data as JSON: /api/errors/a5579ee68ff5edf1.
Report an issue: GitHub.