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
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