1. We need to adjust Dfsck to the new per-file replication feature.
fsck checks block replication based on the configured global replication parameter.
Which is now just the default. The actual file replication is returned in DFSFileInfo.
So at least the reporting is screwed by that, although I didn't check what will happen with
other options -move and -delete.
2. fsck throws NullPointerException if you type
bin/hadoop fsck -files /doc
bin/hadoop fsck /doc -files
3. Unfortunately, there are several commands that throw different kinds of Exceptions
rather than at least printing the usage info, when some of its arguments are missing or
misplaced. ArrayIndexOutOfBoundsException is one them. Try
bin/hadoop dfs -mv
bin/hadoop dfs -cp
bin/hadoop dfs -rm
4. In general the shell is growing and getting more sophisticated.
Should we work out a general convention on how the parameters should be structured, named,
short/long version of the keywords, help, etc.