Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.0.0-alpha
-
None
-
None
-
None
Description
Currently, fsck does not accept URIs as paths.
[hdfs@cs-10-20-192-187 ~]# hdfs fsck hdfs://cs-10-20-192-187.cloud.cloudera.com:8020/user/ Connecting to namenode via http://cs-10-20-192-187.cloud.cloudera.com:50070 FSCK started by hdfs (auth:KERBEROS_SSL) from /10.20.192.187 for path hdfs://cs-10-20-192-187.cloud.cloudera.com:8020/user/ at Thu Aug 16 15:48:42 PDT 2012 FSCK ended at Thu Aug 16 15:48:42 PDT 2012 in 1 milliseconds Invalid path name Invalid file name: hdfs://cs-10-20-192-187.cloud.cloudera.com:8020/user/ Fsck on path 'hdfs://cs-10-20-192-187.cloud.cloudera.com:8020/user/' FAILED
It'd be useful for fsck to accept URIs.
Attachments
Attachments
Issue Links
- duplicates
-
HDFS-2219 Fsck should work with fully qualified file paths.
- Closed