You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Andy Isaacson (JIRA)" <ji...@apache.org> on 2012/06/01 20:35:23 UTC
[jira] [Created] (HDFS-3489) hdfs fsck usage message is outdated
Andy Isaacson created HDFS-3489:
-----------------------------------
Summary: hdfs fsck usage message is outdated
Key: HDFS-3489
URL: https://issues.apache.org/jira/browse/HDFS-3489
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.0.0-alpha
Reporter: Andy Isaacson
Assignee: Andy Isaacson
Priority: Minor
The help message from "hdfs fsck" is misleading in several ways.
{code}
Usage: DFSck <path> [-list-corruptfileblocks | [-move | -delete | -openforwrite] [-files [-blocks [-locations | -racks]]]]
<path> start checking from this path
-move move corrupted files to /lost+found
-delete delete corrupted files
-files print out files being checked
-openforwrite print out files opened for write
-list-corruptfileblocks print out list of missing blocks and files they belong to
-blocks print out block report
-locations print out locations for every block
-racks print out network topology for data-node locations
By default fsck ignores files opened for write, use -openforwrite to report such files. They are usually tagged CORRUPT or HEALTHY depending on their block allocation status
Generic options supported are
-conf <configuration file> specify an application configuration file
-D <property=value> use value for given property
-fs <local|namenode:port> specify a namenode
-jt <local|jobtracker:port> specify a job tracker
-files <comma separated list of files> specify comma separated files to be copied to the map reduce cluster
-libjars <comma separated list of jars> specify comma separated jar files to include in the classpath.
-archives <comma separated list of archives> specify comma separated archives to be unarchived on the compute machines.
The general command line syntax is
bin/hadoop command [genericOptions] [commandOptions]
{code}
- the first line should not say "DFSck"
- the -fs option prefers a hdfs:// URI rather than a bare namenode:port pair
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3489) hdfs fsck usage message is outdated
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288029#comment-13288029 ]
Eli Collins commented on HDFS-3489:
-----------------------------------
Per HDFS-3483 it should require a file system with scheme hdfs.
> hdfs fsck usage message is outdated
> -----------------------------------
>
> Key: HDFS-3489
> URL: https://issues.apache.org/jira/browse/HDFS-3489
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Andy Isaacson
> Assignee: Andy Isaacson
> Priority: Minor
>
> The help message from "hdfs fsck" is misleading in several ways.
> {code}
> Usage: DFSck <path> [-list-corruptfileblocks | [-move | -delete | -openforwrite] [-files [-blocks [-locations | -racks]]]]
> <path> start checking from this path
> -move move corrupted files to /lost+found
> -delete delete corrupted files
> -files print out files being checked
> -openforwrite print out files opened for write
> -list-corruptfileblocks print out list of missing blocks and files they belong to
> -blocks print out block report
> -locations print out locations for every block
> -racks print out network topology for data-node locations
> By default fsck ignores files opened for write, use -openforwrite to report such files. They are usually tagged CORRUPT or HEALTHY depending on their block allocation status
> Generic options supported are
> -conf <configuration file> specify an application configuration file
> -D <property=value> use value for given property
> -fs <local|namenode:port> specify a namenode
> -jt <local|jobtracker:port> specify a job tracker
> -files <comma separated list of files> specify comma separated files to be copied to the map reduce cluster
> -libjars <comma separated list of jars> specify comma separated jar files to include in the classpath.
> -archives <comma separated list of archives> specify comma separated archives to be unarchived on the compute machines.
> The general command line syntax is
> bin/hadoop command [genericOptions] [commandOptions]
> {code}
> - the first line should not say "DFSck"
> - the -fs option prefers a hdfs:// URI rather than a bare namenode:port pair
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira