- Joined
- Mar 6, 2014
- Messages
- 9,553
Actually, it seems like that's exactly what happens: the zfsacl vfs object does break Unix permissions, at least partially.
I realize this thread is starting to get a bit old, but what FlynnVT was describing as his problem was almost exactly what I was finding on my CIFS shares with Unix permissions: users could create new files, but modifying existing ones proved troublesome. I was glad to see that I wasn't the only one having this problem, so I dug into it a bit more on a test system, and I was able to reliably reproduce serious permissions problems due to "zfsacl" being set on my CIFS share, which was using Unix permissions.
I filed bug report #11390, and much to my surprise I was told that Unix permissions are not supported with CIFS shares, period. The bug goes on to request a documentation change because I don't think this is made clear in the official docs.
I just wanted to share that critical bit of information right here because several people in this thread seem be under the impression (as I was until very recently) that Unix permissions ought to work fine with a CIFS share when, in fact, this is not the case, and the FreeNAS developers never intended the Unix/CIFS combination to be used at all. Knowing that would have saved me a bunch of headaches.
Thanks for posting this. I was wondering why they didn't allow removing that particular vfs object and its related nfsv4 parameters. I'll adjust advice to people experiencing permissions problems accordingly. Considering the constant problems people seem to have with permissions, it's probably wise to just focus on supporting a single permissions type and make sure it works properly.