On NFS V4.1 mounted file systems 'mkdir(1M)' can return incorrect status if setgid bit is enabled.
(Doc ID 2901485.1)
Last updated on OCTOBER 12, 2022
Applies to:Solaris Operating System - Version 11.3 and later
Information in this document applies to any platform.
A customer admin encountered a problem creating directories on NFS v4.1 mounted file systems.
The mkdir(1M) command would return unexpected / incorrect status when trying to create sub-directories in a NFS mounted directory which had the SETGID bit enabled.
For example, they would login to zone <zone1> and cd to /nfs/users/user1 and then create a directory as follows:
Customer had been using NFS V4.0 and had recently moved and re-mounted their NFS file systems using NFS 4.1 due to a NFS file server architecture change.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document