maindavfs2 - Support: sr #109564, davfs2 retains 'read' permission...


sr #109564: davfs2 retains 'read' permission on the mounted files

Submitter:  PrasannaBhat <prasannabhat>
Submitted:  Thu 20 Sep 2018 11:20:20 AM UTC
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Need Info
Privacy:  Public Assigned to:  _71007
Open/Closed:  Open Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment (Rich Markup)

Fri 21 Sep 2018 10:11:04 AM UTC, comment #4: 

I don't understand what you mean with "mount folder" and "original file". Please describe in more detail. Best would be an example with real file and directory names.

Before mounting:
What is the mount point; what the WebDAV-server?

The exact command, settings in fstab and davfs2.conf, mounting user?

After mounting:
What did you expect for which file? what do you instead get?


- <_71007>
Fri 21 Sep 2018 05:44:04 AM UTC, comment #3: 

Thanks for the reply. My question here is, how we can make the mount folder reflect the exact file permission of the original file? Permissions of the original file can be changed after the file system is mounted, but the latest file permissions are not being reflected properly on the mount location. Any settings we need to do here for reflecting the current permissions of the file on to mount path ?

PrasannaBhat <prasannabhat>
Thu 20 Sep 2018 04:31:07 PM UTC, comment #2: 

The mode of the mountpoint does not influence the mode of the mounted file system. It is completely independend.

By default:
Owner of the file system is the mounting user, group is the primary group of the mounting user and the mode of files and directories is derifed from the umask variable of the mounting user.

Non default:
You can use the mount options uid, gid, file_mode and dir_mode to set this values at mount time.

Please see "man mount.davfs" for details.


- <_71007>
Thu 20 Sep 2018 11:24:11 AM UTC, comment #1: 

Can you please help to understand, how we can retain the original file permissions in the mounted path?

PrasannaBhat <prasannabhat>
Thu 20 Sep 2018 11:20:20 AM UTC, original submission:  


When we mount a linux direcotory using davfs2, then the original file permissions are being altered on the mounted path. For example, if a file - File1.txt has 000 pemission on it, when it is mounted onto say /mnt/mount path as some user User1, then when we check the permission of the File1.txt in /mnt/mount path, it shows 444 (i.e only READ access is available for all users). But you cant copy the file from the path /mnt/mount because it fails with error - cannot open `File1.txt' for reading: Invalid argument

This means, File1.txt is being wrongly shown as having read permission on the mounted path. So, davfs2 mount is adding a default read permission on the files in the mounted path but in reality, that file dont have the read permission.

Can you please help to understand, how we can retain the original file metmissions in the mounted path?

PrasannaBhat <prasannabhat>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by _71007 (Posted a comment)
  • -email is unavailable- added by prasannabhat (Submitted the item)
  • -email is unavailable- added by prasannabhat

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.





    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-12-26 _71007 StatusIn Progress Need Info
    2018-09-21 _71007 StatusDone In Progress
    2018-09-20 _71007 Severity4 - Important 3 - Normal
    2018-09-20 _71007 StatusNone Done
        Assigned toNone _71007
    2018-09-20 prasannabhat Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.11