When debugging the FSImage corruption issue, I often need to know a file's or directory's inode id. At this moment, the only way to do that is to use OIV tool to dump the FSImage and look up the filename, which is very inefficient.
Here I propose adding option "-i" in FsShell that prints files' or directories' inode id.
fileId exists in HdfsLocatedFileStatus, which is already returned to hdfs-client. We just need to print it in Ls#processPath().
For file:// (Local FS)
Windows has the concept of "File ID" which is similar to inode id. It is unique in NTFS and ReFS.
The fileId entry will be "0" in FileStatus if it is not set. We could either ignore or throw an exception.