Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Setting Volume Permission Recursively does not work

  1. #11
    Junior Member
    Join Date
    Jan 2012
    Posts
    11

    Unhappy

    I confirm - it does not work with 8.0.3

  2. #12
    Senior Member
    Join Date
    Sep 2011
    Posts
    416
    Quote Originally Posted by Ico747 View Post
    I confirm - it does not work with 8.0.3
    Yeah.. this needs more work, but it will be 8.2.1+. For now, please trust your tool that you're using to set the permissions correctly (Explorer, Finder, console, etc).

  3. #13
    Junior Member
    Join Date
    Jan 2012
    Posts
    11
    Quote Originally Posted by gcooper View Post
    Yeah.. this needs more work, but it will be 8.2.1+. For now, please trust your tool that you're using to set the permissions correctly (Explorer, Finder, console, etc).
    Tank you very much for your answer. I am new in freenas and freebsd. Do you mean that using other tools I could get the same result. Could you please give an example how to with console?

  4. #14
    Senior Member
    Join Date
    Sep 2011
    Posts
    416
    Quote Originally Posted by Ico747 View Post
    Tank you very much for your answer. I am new in freenas and freebsd. Do you mean that using other tools I could get the same result. Could you please give an example how to with console?
    Np.

    The best recommendation I can give is:

    1. Don't set permissions recursively and permissively (setting permissions non-recursively works well).
    2. Use your preferred weapon of choice to restrict permissions, whether it is Explorer, Finder, Konqueror, Thunar, etc. If you want to use the command line tools, here are some manpages for using chmod [1] and chown [2]. The setfacl/getfacl manpage is very incomplete (it doesn't describe all of the settable ACLs.. I have a PR open for that)

    1. http://www.freebsd.org/cgi/man.cgi?chmod
    2. http://www.freebsd.org/cgi/man.cgi?chown

  5. #15
    Junior Member
    Join Date
    Sep 2011
    Posts
    15
    Recursive permission still seems broken in 8.0.4 as well

  6. #16
    Junior Member
    Join Date
    Nov 2011
    Posts
    7
    Indeed, I too am having issues when attempting to set permisions recursively via the GUI.

    If the dataset has any significant size at all (say 100GB), after click the "Change" button on the modal permissions window, the the window just hangs and sits there. I can close it, but none of the permissions are changed.

    Since this appears to be broken, I am wondering if it is perfectly safe to run a chown -R command on the dataset. Will it break any permissions issues with the ZFS dataset? Or will it work fine?

    Example : "chown -R nobody:storageaccess /mnt/storage/dataset" <- Is this safe?

    My freenas version is FreeNAS-8.0.4-RELEASE-x64 (10351).

  7. #17
    Junior Member
    Join Date
    Apr 2012
    Posts
    8
    with FreeNAS-8.0.4-RELEASE-p1-x64 the same issue not working from GUI - stacking without any message for long period of time without changing nothing
    only by using chown from console - ok

  8. #18
    Senior Member
    Join Date
    Jun 2011
    Posts
    100
    I'm still using FreeNAS-8.0.3-p1 (Multimedia edition) and I succesfully changed permissions recursively on an entire dataset using the gui. It takes a very long time, but it gets the job done. If you watch the output of 'top', you will see that a python script gets a lot of cpu resources. That's the one changing the permissions. If it finishes and you then you check the permissions, you will see they are changed.

    So you just need to wait a very long time, depending on the size of your dataset.
    Gigabyte Motherboard GA-D525TUD, Atom D525 1.8Ghz (Dual Core)| 4GB RAM| Lian Li PC-Q08B Case| 4 x WD green 2TB (WD20EARS) in RaidZ

  9. #19
    Junior Member
    Join Date
    Apr 2012
    Posts
    8
    agree, with FreeNAS-8.0.4-RELEASE-p1-x64 probably the same issue as stated by sjieke, I would say never was waiting till end of GUI operation, for huge amount of data it doing so long and really I don't see any sign of operation in progress.
    Using console chown, chmod working faster.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •