ZFS issues working in conjunction with SourceGear Vault

[OldDude]

I've had FreeNAS up and running for about 6 months now. (v8.04-release) and everything has been fine until recently when our Engineers changed the way they've been working with the storage.

I have a single ZFS volume with a CIFS share that is configured for anonymous access for everyone within the company network.

Any files copied or moved onto the NAS location are accessible and modifiable regardless of whether the clients were Linux, Windows or Mac based. However, we've discovered that if the NAS is referenced as the 'working' directory to check files out of our version control system (SourceGear Vault Pro) the files all become un-modifiable. They can be read, or copied off the NAS, but the only way they can be edited or deleted is if I access them via the console.

From the console, I can see that the access permissions are all -rwxrwxrwx, but if I try to access them from a client the access rights are displayed as unknown.

Since this only occurred when using the SourceGear Vault software, I originally put the blame in their laps. However, I've discovered that if I create a UFS Volume and configure the CIFS share identically there are no problems whatsoever.

Am I missing something here? I can't see why ZFS versus UFS would have an impact on file access permissions. I want the ZFS features and do not look forward to having to build a 2nd system and migrate everything over to a UFS system.... that's like taking a step backwards as far as I'm concerned.

Does anyone have any ideas as to what I can do to correct this?

Thx

 

[paleoN]

However, we've discovered that if the NAS is referenced as the 'working' directory to check files out of our version control system (SourceGear Vault Pro) the files all become un-modifiable. They can be read, or copied off the NAS, but the only way they can be edited or deleted is if I access them via the console.

Can't say I've ever used SourceGear Vault, but it sounds similar to this.

From the console, I can see that the access permissions are all -rwxrwxrwx, but if I try to access them from a client the access rights are displayed as unknown.

Since this only occurred when using the SourceGear Vault software, I originally put the blame in their laps. However, I've discovered that if I create a UFS Volume and configure the CIFS share identically there are no problems whatsoever.

Which means the *nix permissions aren't the issue. The problem is the Windows ACEs. What are the reported advanced permissions for the affected/all accounts? I say reported as CIFs fakes some of the permission options.

I didn't think CIFs worked any different with ZFS vs. UFS. Are you sure the shares are identical? How about setting up an additional share in a different folder on ZFS using the same steps you did for UFS.

 

[OldDude]

paleoN, thanks for your response.

I didn't expect that many people would have experience with both FreeNAS and SourceGear's Vault but I felt it was necessary to specify that the issue I was having wasn't related to "normal" Windows/Mac/Linux operations but specifically when file functions were handled with a particular application.

I agree that the issue lies in the ACEs and in response to your question the reported advance permissions are labelled as 'special' for all roles. Looking at the individual Permissions only the Deny features for 'Write Attributes', 'Write Extended Attributes', 'Change Permissions' and 'Take Ownership' are selected.

To test my theory that the issue appears to be related to the ZFS versus UFS configuration, I obtained an unused computer and set up a small temporary FreeNAS device for testing. I built the entire system and logged the process so that I could replicate each step when I reconfigured the machine again.

Configured using ZFS and CIFS sharing I was able to duplicate the error I see on the production NAS.

I then rebuilt the entire array but instead used the UFS volume. Configured the CIFS share the same way (tho' I changed the volume name reference to ensure I didn't have any cached references on the client side) and the system works flawlessly without any errors.

To me this proves that there is fundamentally something different at the ZFS/UFS level that impacts or impedes the share interpretation. CIFS can obviously permit whatever permission operations are being performed because it does so successfully when applied to a UFS volume. So, I have to assume that the issue resides somewhere within ZFS.

Any ideas?