Changing a dataset between Windows and Unix permissions

[Crispin]

Hi folks,

I'm not sure if this is a bug / issue or by-design

If I create a dataset as Unix share I can manage the permissions as expected. I can do this:

If I create a dataset as Windows permissions it's as-expected with everything else greyed out.
However, it allows me to change it back to Unix share.

When I do this the permissions appear to work as-expected but the "Other" is always stuck on Read and Execute - no matter how much you change it. Reload and it's back to:

As such, setting something to -r for other has no effect even though it looks like it did.
This is quite repeatable.

I've been struggling to get the permissions to work well. I thought I was being daft but I suddenly remembered that I created these as Windows permissions and not Unix about 2-3 years ago.

I'm no expert on Unix permissions so apologies if I got this wrong.

My system - latest updates on 9.10

Thanks
Crispin

 

[dlavigne]

This is by design, to prevent the user from inadvertantly clobbering the Windows ACLs.

 

[Crispin]

Thanks for the reply.

Admittedly, I've been reading up more on this and things are becoming clearer.

Can I confirm something then -
based on my thoughts from the post I recreated all of the datasets which were windows shares and created unix shares. I copied the contents from old into new but now have even weirder problems.
I assume that the ACLs are still against the files and that I have created a world of pain for myself? What's the best solution for fixing all of this mess?

Base on another thread I had it's suggested I stick with only Unix as I have use the files from both Windows and *nix machines.


TIA

Crispin

 

[anodos]

Base on another thread I had it's suggested I stick with only Unix as I have use the files from both Windows and *nix machines.

That is incorrect. The permissions type has absolutely nothing to do with the OS of client machines.

The only effect this setting has is to alter the zfs "aclmode" property for a dataset. When the dataset is set to "Windows" then the aclmode gets set to "restricted". Aclmode=restricted stops chmod from breaking ZFS ACLs.

 

[Crispin]

Ok, now I'm confused :(

I thought you said, seeing as I use loads of different ways to read and write to the files - that is, the same set of files gets used by windows clients, freebsd (backup scripts copying files offsite) and apache in jails - that I should stick with unix-only - aclmode != restricted. It would be be best.
Have I misunderstood?

Aclmode=restricted stops chmod from breaking ZFS ACLs.

That explains what what the difference is. thanks. Makes it a bit clearer now.