Looks like you are running out of space. While running SSET, it creates the fp file, which is likely to be of the size that you specified. But, you may need 3 times that space on your device to successfully complete this task. For example, if the fp file is 10GB, the tool will take an additional 10gb for temporary files, and another 10GB for fp_sorted file. Thus you may need 30GB of free space.
If it is a free space issue, the tool does not seem to be doing what it is supposed to with the flags, since I had used the -f and -T options, which are supposed to put the fingerprint file and the temp files in the designated location. (Unless the free space is absolutely needed on the local C:\ drive, which I assumed it would not need since I told it to save the log and temp file to a different mapped drive.)
I am *not* getting the”;No Space Left on Device” error message, which the Readme says would be displayed if the temp space filled up.
In addition to the two previous runs, I tried this variation, running the find_space.exe from the same directory as where the log file set to be saved:
Where Y:\ is a NetApp CDOT CIFS share, and Z:\ is also a NetApp CDOT CIFS share The fp2.fp2 is created on the y:\ drive. The Y:\ drive has +300GB free. I don't think it should matter, but the Z:\ drive does have +100GB free also. The local drive only have about 15GB free.
Unfortunately the KB article you linked is restricted:
Article Not Found The article was not found, is restricted to NetApp employees and partners, or is no longer available.
I suppose I'll try changing the Windows temp space to a remote location and trying again, but I am not getting an out of space message.