On the Hey Scripting Guy! blog at Technet, Chad Miller reports that if you run a Windows Powershell command as a SQL Agent job, and there are no syntax errors yet, the command produces an error (for example, attempting to get operating system information from an unavailable server). The SQL Server Agent job will report success.
Check tip #10 in the post for instructions on how to implement error handling with different options so that you can, for instance, have SQL Agent continue on error or halt the Agent job. The reported "succeeded" may not in fact have succeeded.

10-tips-for-the-sql-server-powershell-scripter

SQL agent job, why is the job history showing that a step is still running even though the job has completed
Typically non-root users cannot mount directories. 

Running Redhat 
Have 6GB tar.gz (/dir/somefile.tar.gz)
Need to move to a NFS share on another box (//somebox/somefolder/)

We have no other access. 

Any ideas? 
