File permissions

Hooverdan · May 17, 2023, 9:11pm

Interesting. I checked on one of my setups and noticed something similar. The Rock-on had modified (I believe) the ownership of that directory, however in the UI the original setup was still present:

Now, when I changed the owner (chown) via the UI, the terminal and UI output were in sync:

as for the permissions, those apparently remained the same as originally set:

server:/mnt2 # stat -c '%A %a %n' minecraft
drwxr-xr-x 755 minecraft

vs. UI

now, changing the permissions via terminal to a different value, say:
drwxrwxr-x 775 minecraft

the value remains the same as before in the UI (755) - as you have observed.

Now, when I change the permissions via the UI to, say, this:

now, via terminal you can see the change:
drwxr--r-- 744 minecraft

Without photographic proof I can also confirm that all sub-directories and files have that permission change applied.

So, I think, this means that during the initial setup of a share or changes of the attributes, that information is stored on the Rockstor database and applies to the root directory of the share. If no terminal-level meddling occurs, those would remain in sync.
However, if those owners and permissions are changed without going through the UI, they will go out of sync.

Looking at the code (without understanding everything) it seems that during creation a default owner/permission piece is set up (during initial share setup one cannot assign a owner/permission set).

github.com

rockstor/rockstor-core/blob/bdc3df2762ceddf355b482ca50f698654e342861/src/rockstor/storageadmin/views/share_acl.py#L31-L40


      
          def post(self, request, sid):
              with self._handle_exception(request):
                  share = Share.objects.get(id=sid)
                  options = {
                      "owner": "root",
                      "group": "root",
                      "perms": "755",
                      "orecursive": True,
                      "precursive": True,
                  }

After the initial creation of the share, one can go back in and make a change to the owner/permissions.

github.com

rockstor/rockstor-core/blob/bdc3df2762ceddf355b482ca50f698654e342861/src/rockstor/storageadmin/views/share_acl.py#L41-L53


      
          options["owner"] = request.data.get("owner", options["owner"])
          options["group"] = request.data.get("group", options["group"])
          options["perms"] = request.data.get("perms", options["perms"])
          options["orecursive"] = request.data.get(
              "orecursive", options["orecursive"]
          )
          options["precursive"] = request.data.get(
              "precursive", options["precursive"]
          )
          share.owner = options["owner"]
          share.group = options["group"]
          share.perms = options["perms"]
          share.save()

(overriding the previous default values)

Those will be recursively applied to the share (both ownership and permissions).

github.com

rockstor/rockstor-core/blob/bdc3df2762ceddf355b482ca50f698654e342861/src/rockstor/storageadmin/views/share_acl.py#L60-L62


      
          chown(mnt_pt, options["owner"], options["group"], options["orecursive"])
          chmod(mnt_pt, options["perms"], options["precursive"])
          if force_mount is True:

So, obviously in the UI, the display of that information comes from the database under which those UI values were saved. Terminal-based changes on the root share or sub-directories and files are not comprehended or queried. Here is the model, storing that information:

github.com

rockstor/rockstor-core/blob/bdc3df2762ceddf355b482ca50f698654e342861/src/rockstor/storageadmin/models/share.py#LL29-L45


      
          class Share(models.Model):
              # pool that this share is part of
              pool = models.ForeignKey(Pool)
              """auto created 0/x qgroup"""
              qgroup = models.CharField(max_length=100)
              """quota group y/x explicitly created for this Share"""
              pqgroup = models.CharField(max_length=32, default=settings.MODEL_DEFS["pqgroup"])
              """name of the share, kind of like id"""
              name = models.CharField(max_length=4096, unique=True)
              """id of the share. numeric in case of btrfs"""
              uuid = models.CharField(max_length=100, null=True)
              """total size in KB"""
              size = models.BigIntegerField(default=0)
              owner = models.CharField(max_length=4096, default="root")
              group = models.CharField(max_length=4096, default="root")
              perms = models.CharField(max_length=9, default="755")
              toc = models.DateTimeField(auto_now=True)

So, in summary, you are right, the UI view and what you have in the share can be out of sync, once the terminal becomes involved. I also believe, that the forced recursion of any changes via the UI (Owner and/or Permissions) can time out when it needs to be applied to a large set of directories/files that already exist on that share…
So, for better or worse, whatever you do with the terminal is the one the system honors. How to get the UI entries realigned or whether that’s even a desirable functionality, since the terminal use is not a standard use case, is worth a discussion.