Permissions not working

[marv]

I can't write to my AFP share, so I am trying to reset the permissions on the volume. When I click the 'change' button, it just clears all the check boxes and errors with 'This field is required'. I've tried different versions etc but to no avail. Can anyone tell me what's going on please?



Ideally I would like to have full access for anyone so you don't have to issue a username and password, but I cannot for the life of me find out how I would go about this...?

 

[matlock]

Select all three check boxes for owner and other. I also believe there is a place to allow anonymous login- I don't have a setup in front of me so I don't have the exacts with details.

 

[marv]

Tried again, with just owner and other checked all three - still says 'This field is required'!

 

[marv]

Anyone got any ideas? I don't understand why I can't do something so simple like set permissions on a volume, despite having reinstalled etc etc... at the point now where I'm going to have to give up and use a different NAS product :(

 

[William Grzybowski]

Let us know how that goes. Good luck.

PS: Stop using BETA software if you're not up to the task.

 

[marv]

Actually, William, I get the same on both Beta and older versions. If you can't be bothered to offer any help, don't litter the forum with rude messages.

 

[William Grzybowski]

If you can't be bothered for no one offering help don't come here saying you won't be using this product anymore. Just don't.

Oh, and no, you don't get that on 8.0.4-RELEASE-p3, don't try to fool me. In that subject I can say I am an expert, with all due respect ;)

 

[marv]

Well, that doesn't make any sense. I said at the top of this thread that I have 'tried different versions', but clearly you didn't read it. If I say I am thinking about using another product, I'm not trying to hurt anyone's feelings, I'm simply stating what I may be required to do, for the benefit of those reading. It really grinds my gears when you get tetchy unhelpful people in the opensource community, it does no favours for all those who put so much effort into it.

If I give up on FreeNAS due to a lack of help, then that is one unhappy user who will share their experiences with others, for this reason I make it clear of my intentions to give people the opportunity to offer words. If you're going to get upset, you're better off just reading the forums and not posting.

 

[William Grzybowski]

"Everybody lies". Dr. House

You lied :). The screenshot you've posted is an error exclusive of BETA.
If you do not have the moral to admit you were using 8.2 BETA for this screenshot then I feel sorry for you.

Good luck
(not going to reply this thread anymore per your gentle request)

 

[marv]

I believed that I was running 8.0 the first time and got the same error. If it is impossible to get this error in earlier versions and it is a known bug, why not just tell me? Maybe I have made a mistake rather than telling deliberate lies? What benefit would I get from purposefully posting incorrect information when asking for help???

I will try an older version and make absolutely certain of the version I am running...

 

[paleoN]

Congrats on pissing off William, FN8 dev, and possible your best chance at getting this to work ;)

[OT]
Anyone else think it would be helpful if the FreeNAS people had special designations saying as much?
[/OT]

What are the current permissions on that folder? From an SSH session as root:

Code:

ls -al full path to folder

Put in the actual path to the folder obviously.

 

[marv]

The permissions were showing as read only for all but the owner. Trying to reapply permissions from the GUI just appeared to hang on 8.0.4 without the error message I received on the beta (left it overnight, but the lightbox window was still active). Logged in to the shell as root and did a chmod -R 777 * and this seems to have fixed it.

Thanks for your help paleoN (and I should add that it wasn't my intention to upset William! ;)

 

[motoxer913]

I'm having this exact same problem and I'm not on a beta version. It happened after upgrading from 8.0.4 to 8.2.0 release. Since then I have been unable to change my permissions in the GUI. I only noticed because I lost write permissions after the upgrade and because I cannot figure out how to edit my permissions I now only have a read only NFS...really annoying. Would love some help trying to figure out how to resolve this bug.

 

[motoxer913]

I just updated Firefox to 14.0.1 and now this bug is gone and I can finally set permissions again. So, I'm guessing this is a browser issue.
FYI there is a better discussion of the same problem going on here...suggestion people use this thread instead:
http://forums.freenas.org/showthread.php?7634-Can-not-modfy-AFP-Users/page5

 

[paul]

CHMod

Ok try this


you need to ssh or (shell from the GUI)

Code:

chmod -R 770 /mnt/Drivepoolname/folder

770 means that only placemaster (owner) and group members have full access to defined files and folders

 

[brossow]

I get this error in the current release. Symptoms are EXACTLY as those described by others so no need to repeat. Error persists regardless of browser (tried with latest release versions of Chrome, Safari and Firefox on MacBook Pro running OS X 10.8.1 with all available system updates). I can change the permissions with chmod at the command line without issue, but of course new subdirectories and files do not inherit the correct permissions.

Note that this applies to changing the permissions via the Storage tab. If I change the permissions from the Shares tab under AFP, it works as expected. Note also that there is a defect ticket for this issue that is closed but probably shouldn't be.

System Information
Build: FreeNAS-8.2.0-RELEASE-p1-x64 (r11950)
Platform: AMD E-350 Processor
Memory: 7775MB

 

[pmendelski]

Hello everybody,

Just to let you know that this problem still exist in the current Release 8.3.1 and I have narrowed this issue to the order of creating shares and user settings that are mapped to those shares. I think it has happened to me when I have one 'user' mapped as the one entitled to use Apple Timemachine Share with path to his home directory set as Timemachine folder. And then I think I set 'do not use home directories' or home directory to /nonexistent ... it would then corrupt all logical inheritance of permissions for this user to share and volumes. I have lost ability to set any permissions to users, groups, shares, and volumes, even after reboot of freeness, browser cache clear, restarting services, deleting volumes and recreating again, deleting all shares and recreating again etc via GUI. There was simply no virtual way to get this back on track and get the permissions working again. They would be just greyed out boxes with no option to select them.

If anyone will get himself into the same pickle ... I found the only way to restore the permissions again is by restarting an installation of freenas from live cd or iso image and in the step when you are asked if you would like to import your settings file say yes. It will bring all you freenass to where it was with all permissions working again :D

 

[Pmart]

So I ended up here (for the first time) based off a Google search for a similar issue. I actually took 10 minutes out of my day to register because it seems to me that William is a giant prick that really shouldn't be "helping" people. This server runs pretty badly. Is is freenas beta?

 

[diedrichg]

So I ended up here (for the first time) based off a Google search for a similar issue. I actually took 10 minutes out of my day to register because it seems to me that William is a giant prick that really shouldn't be "helping" people. This server runs pretty badly. Is is freenas beta?

You just replied to a thread that was started 2 years, 5 months ago and was last replied to 1 year, 8 months ago and references builds that are around 18 revisions ago.

 

[Ericloewe]

So I ended up here (for the first time) based off a Google search for a similar issue. I actually took 10 minutes out of my day to register because it seems to me that William is a giant prick that really shouldn't be "helping" people. This server runs pretty badly. Is is freenas beta?

How about you ask for help properly instead of crying about perceived slights from 20 months ago? Open a thread and tell us what's wrong.