This content has been marked as final. Show 1 reply
The Solaris implementation of NFS has always been very strict.
Other OS's? Not so much. Put an inode number larger than 32 bits while using non-large-file-aware NFSv2, like Irix would do? A Solaris host couldn't access the file. Nevermind some of the sketchy NFS sleight-of-hand Linux has been known to pull (silently truncating group membership?!?!?!).
And NFSv4 is pretty complex, and in my experience too easy to break.
I'd open tickets with Oracle and NetApp, and see if you can get something more out of them than pointing fingers at each other.