NFS Share and file permissions

Status
Not open for further replies.

gak

Cadet
Joined
Mar 13, 2013
Messages
2
We are trying out FreeNAS as a backup to disk device. Backing up to an HP Proliant running the release candidate 8.3.1, and trying to write to it from a Windows 2008 R2 server running Backup exec, backing up to disk.

I was trying to use NFS as from what I have read it should be faster (and does seem to be compare to earlier tests).

It is mostly working except one final hurdle is driving me nuts. The share can be accessed, backup image files are created, but they cannot be written to. When I check file permisssions on newly created files they are all '-rwxr-xr-x' User can write, but group and other cannot.

If I chmod 777 all the files, everything starts working until the backup process creates new images, which are created with the above permissions, and stay at 0 bytes in size till I chmod them all.

I have the ZFS volume with the below permissions. I have tried checking off the recursive option.

ScreenHunter_09 Mar. 13 22.55.jpg

I created a dataset on the volume with the below permissions. I have tried checking off the recursive option.

ScreenHunter_09 Mar. 13 23.02.jpg

The NFS share is configured as below. Was hoping that using mapall as root would avoid conflicting user name/permission problems. We'll come back to permissions once we proove the concept.

ScreenHunter_09 Mar. 13 23.04.jpg

And I have the option for the NFS service checked to allow non root mount.

I've tried chown from the cli to assign root:wheel to the folders recursively, and chmod recursivley.

Just every time a new file is created in the share, it is not writeable in the 'group' or 'other' position, and our backups stop.

Not sure what I can do to correct that, or am I looking at this the wrong way? I'm just trying to set it up quick and wide open just to see if this will work for us on larger quantities of data.

Any suggestions would be greatly appreciated!

Thanks,

Glenn
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
What are the permissions of the folder you are trying to share? If you do chmod 777 foldername I think that will fix your problem.
 

gak

Cadet
Joined
Mar 13, 2013
Messages
2
What are the permissions of the folder you are trying to share? If you do chmod 777 foldername I think that will fix your problem.

Yeah, I have tried that. Thanks though!

I have tried "chmod 777 /mnt/vol1/backups-nondd", "chmod 777 /mnt/vol1", and even "chmod 777 /mnt". I have also tried chmod -R to make it recursive, at each level, and still having the same problem.

I have tried chown at each level as well.

There is one additional folder in play. The backup process creates a subfolder, so the full path to the files is "chmod 777 /mnt/vol1/backups-nondd/B2D1" and I've clobbered that one with permissions as well.

It starts off creating the "changer.cfg" file and the "folder.cfg" file. I have to chmod them to 777 and then it starts creating a bunch of "bkf" images that it wants to write all the data to. Then it starts to look like this, and it will just keep creating new bkf files till it can finally write to one. (Ignore all the dates and times. I'm just re-creating what I saw).

-rwxr-xr-x 1 root wheel 0 Mar 13 16:27 B2D000001.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:28 B2D000002.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:34 B2D000003.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:34 B2D000003.lck
-rwxrwxrwx 1 root wheel 128 Mar 13 17:23 Changer.cfg
-rwxrwxrwx 1 root wheel 342 Mar 13 15:41 Folder.cfg
[root@freenas /mnt/vol1/backups-nondd/B2D1]#

I'll chmod 777 all the files and then the backup process starts working and looks like this.

-rwxrwxrwx 1 root wheel 2147362816 Mar 13 16:27 B2D000001.bkf
-rwxrwxrwx 1 root wheel 2147362816 Mar 13 16:28 B2D000002.bkf
-rwxrwxrwx 1 root wheel 962816 Mar 13 16:34 B2D000003.bkf
-rwxrwxrwx 1 root wheel 0 Mar 13 16:34 B2D000003.lck
-rwxrwxrwx 1 root wheel 1028 Mar 13 17:23 Changer.cfg
-rwxrwxrwx 1 root wheel 2042 Mar 13 15:41 Folder.cfg
[root@freenas /mnt/vol1/backups-nondd/B2D1]#

When the last file 'fills up' it starts creating new bkf files, but they don't seem to be writeable, at least not for group and other. Writeable in the user position.

-rwxrwxrwx 1 root wheel 2147362816 Mar 13 16:27 B2D000001.bkf
-rwxrwxrwx 1 root wheel 2147362816 Mar 13 16:28 B2D000002.bkf
-rwxrwxrwx 1 root wheel 2147362816 Mar 13 16:34 B2D000003.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:27 B2D000004.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:28 B2D000005.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:34 B2D000006.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:27 B2D000007.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:28 B2D000008.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:34 B2D000009.bkf
-rwxr-xr-x 1 root wheel 0 Mar 13 16:34 B2D000009.lck
-rwxrwxrwx 1 root wheel 1028 Mar 13 17:23 Changer.cfg
-rwxrwxrwx 1 root wheel 2042 Mar 13 15:41 Folder.cfg
[root@freenas /mnt/vol1/backups-nondd/B2D1]#


The files that are there keep the permissions that I manually set, even after they are touched again during our backup process. New files just don't seem to get it! I have to chmod the files and then it starts writing to them.

I believe if it could write to the first 'bkf' file it creates, it would only create one at a time. That is what I have seen happen elsewhere. It seems be creating multiple bkf files in an effort to find one it can write to.

I'm not sure why the group position of permissions is hanging up what should be root user permissions anyway.

Hope the extra information provides more insight...

Thanks,

Glenn
 
Status
Not open for further replies.
Top