all new creations folders or any media has 611 permissions

[Kevin Galbraith]

So I have searched around and cannot find anything similar to this.

My pervious media server died, a centos VM running on VMWAre. I decided to create a baremetal Freenas server to hold all of my media and what ever else I might come across. Since the server is in a locked down enviroment, I created the volumes default root/wheel with 777 permissions. I installed the jails with the credentials. The problem I am having is that anything created has 611 permissions instead of 777. Thus, any downloads sabnzbd processes fails. I confirmed this by dropping to console and touching a file in a media directory and saw the permissions as ls


I have no idea why this is happening and I have no idea how to fix it. I have since added and re-added the jails. I have not destroyed the media volume mostly because there is already 2TB of stuff on it.

 

[Robert Trevellyan]

I created the volumes default root/wheel with 777 permissions

Please be more specific. Are you talking about the permissions on the dataset(s) that's mounted in the jail(s)?

I installed the jails with the credentials

What does this mean?

 

[Kevin Galbraith]

Please be more specific. Are you talking about the permissions on the dataset(s) that's mounted in the jail(s)?

This means that I created a new volume, within that volume I have multiple data sets for different types of media. Since the server is in a secure environment I set the permissions to 777 recursively from the volume through the data sets.
When Sabnzbd gets done processing and moves a file, it is creating files with 611 permissions. I have sab set to make all new files 777, but it does not seem to be working. To clarify, I have Freenas permissions set as 777 on every volume/dataset/jail, but folders/media created by my downloader's are not receiving those permissions.

What does this mean?

It mean that after the jail was installed, ie Sabnzbd, I opened up its permissions and set it to 777 and changed the users to root/media. (media being a user I created since that is what sab/sick/couch are running as)


Forgive me if my freenas lingo is a little off. I am new to this distro and am working this out as I go. I not used to primarily using a gui over a shell.

 

[Robert Trevellyan]

I set the permissions to 777 recursively from the volume through the data sets.

Did you set the permissions for each dataset to 777? I don't think a dataset inherits permissions from its parent.

after the jail was installed, ie Sabnzbd, I opened up its permissions and set it to 777 and changed the users to root/media

Are these settings you changed in the plugin's configuration? I'm not familiar with these plugins so you probably need to ask for help in the plugins sub-forum.

One thing that helps with getting plugins working correctly (and checking what they're up to) is to make sure there is a FreeNAS user with the same user ID and group ID as the user the plugin runs under. You can check this using the Display System Processes popup. After installing a plugin, usually you'll find processes running there under an unnamed user ID. You can then create a FreeNAS user with that ID and make sure the storage you give to the plugin is owned by that user. You can see how that works for the BTSync plugin in this thread.

 

[Kevin Galbraith]

Did you set the permissions for each dataset to 777? I don't think a dataset inherits permissions from its parent.

My understand of recursive was that it applies to everything within that tree, but i will apply it to each dataset

Are these settings you changed in the plugin's configuration? I'm not familiar with these plugins so you probably need to ask for help in the plugins sub-forum.

One thing that helps with getting plugins working correctly (and checking what they're up to) is to make sure there is a FreeNAS user with the same user ID and group ID as the user the plugin runs under. You can check this using the Display System Processes popup. After installing a plugin, usually you'll find processes running there under an unnamed user ID. You can then create a FreeNAS user with that ID and make sure the storage you give to the plugin is owned by that user. You can see how that works for the BTSync plugin in this thread.

These are plugins for a media server portion of freenas. I have created the users and the plugins are working just fine. My problem is that permissions I have set to the folder are not applying to new data created in the folder.

 

[Robert Trevellyan]

My understand of recursive was that it applies to everything within that tree, but i will apply it to each dataset

I believe when you apply permissions to a dataset recursively, they are applied to all files and folders but not to child datasets, because a dataset is a distinct filesystem.