inodepath
filer1*> inodepath
usage: inodepath { -v <name> | -f <fsid> | -u <uuid> }
[-ainp] [ -d <snapid> | -s <snapname> ] <inum>
For more information, try ‘inodepath help’ or ‘man inodepath’
filer1*> inodepath help
usage: inodepath { -v <name> | -f <fsid> | -u <uuid> }
[-ainp] [ -d <snapid> | -s <snapname> ] <inum>
Where <inum> and one of -f, -u, or -v are required on the command line and:
-f <fsid> A volume -fsid-
-u <uuid> A volume -uuid- (currently not implemented)
-v <name> A -volume- name
-a List -all- possible names
(default is just the primary name)
-i List parent -info- values
(default is to not list them)
-n List file -names-
(default is to not list them)
-p Do not list -path- names
(default is to list them)
-d <snapid> A -snapshot- name
-s <snapname> A snapshot -id-
<inum> An inode number from the specified volume
(or snapshot within the volume)
For more information, try ‘inodepath help’ or ‘man inodepath’
I honestly can’t see a constructive use for this out in the field or even in the lab!
