violation during recursive put triggers SYS_INVALID_INPUT_PARAM without explanation

[anderbubble]

• [x] master

• [x] 4-2-stable

  If you hit a quota limit during a recursive iput the error returned is SYS_INVALID_INPUT_PARAM, but does not print the "Policy Violation" message seen during a standard iput.

[joan5896@admin2 ~]$ iput -r sfa-upgrade-2019-08-02/
Running recursive pre-scan... pre-scan complete... transferring data...
remote addresses: 10.225.160.101 ERROR: putDirUtil: put sfa-upgrade-2019-08-02/ssfa1a-show-sub-sum-2019-08-02.txt.gz failed. status = -130000 status = -130000 SYS_INVALID_INPUT_PARAM
remote addresses: 10.225.160.101 ERROR: putDirUtil: put sfa-upgrade-2019-08-02/ssfa1a-show-sub-sum-all-2019-08-02.txt.gz failed. status = -130000 status = -130000 SYS_INVALID_INPUT_PARAM
remote addresses: 10.225.160.101 ERROR: putDirUtil: put sfa-upgrade-2019-08-02/ssfa1b-show-sub-sum-2019-08-02.txt.gz failed. status = -130000 status = -130000 SYS_INVALID_INPUT_PARAM
remote addresses: 10.225.160.101 ERROR: putDirUtil: put sfa-upgrade-2019-08-02/ssfa1b-show-sub-sum-all-2019-08-02.txt.gz failed. status = -130000 status = -130000 SYS_INVALID_INPUT_PARAM

[trel]

Ah, probably just need to bubble (ha!) the error stack back to the client.