OD v9.5.0.3
Red Hat Enterprise Linux Server release 6.8 (Santiago)
4 volumes on NetApp, /vol1 250GB and /vol2, /vol3, /vol4 1TB each
The SL is written on /vol1 but actual content on /vol2, /vol3, /vol4 based on round robins. We have re-mounted the volumes now with NOAC and no longer see the 122 error however we are seeing error 119 (Unable to write the file). I am able to see the file at the OS location and pull it in ICN v2.0.3 or hard client. How to get rid of that error message once and for all?
Well CMOD use for System Log the following strategy: he keeps the current file in append mode. So if you go in the cache in the retr/SL directory you will see a link called "APPEND"
so instead of writing tons of small files with the size of a few bytes, CMOD keeps them aggragating in one file until some rules comes, like arsmaint -m, and then it will create a new file to be appended.
Now if you use netapps with some retentions policy where you say, the file is written, and now you cannot touch it, because it is read-only, then CMOD is not happy.
Why? Because a cache is meant to be a cache, not to be a retention FS where you put everything in RO as soon as you touch it.
My advice would be to put some delay (if it is possible) on netapp and tell, wait X hours before putting the file in RO mode. and every X-1 hours, run the arsmaint -m command... and then you will never see such errors again.
but it means you have a window were the file could be modified.