As always when dealing with computers and potentially long running jobs, 
run a test on a handful of files first, so you can rapidly debug.
Did you read the mmfind.README ?

It mentions...that this sample utility "some user assembly required..." 
... 

mmfindUtil_processOutputFile.c
  A utility to parse the "list file" produced by mmapplypolicy and to 
print
    it in a find-compatible format
  mmfind invokes it once mmapplypolicy begins to populate the "list file"

mmfindUtil_processOutputFile.sampleMakefile
  copy to 'makefile', modify as needed, and run 'make' to compile 
mmfindUtil_processOutputFile.c
  This should produce a binary called mmfindUtil_processOutputFile
  mmfind will not be able to run until this utility has been compiled
  on the node from which you launch mmfind.

Works for me...
[root@n2 ilm]# ./mmfind /goo/zdbig -ls
2463649  256 drwxr-xr-x   2 root     root       262144 Feb  9 11:41 
/goo/zdbig
6804497    0 -rw-r--r--   1 root     root            0 Feb  9 11:41 
/goo/zdbig/xy


_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to