Bug 981293 - Cannot change file permissions from windows client
Summary: Cannot change file permissions from windows client
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba
Version: 2.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Raghavendra Talur
QA Contact: surabhi
Depends On:
Blocks: 956495 985406
TreeView+ depends on / blocked
Reported: 2013-07-04 12:15 UTC by Ujjwala
Modified: 2013-09-23 22:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 985406 (view as bug list)
Last Closed: 2013-09-23 22:29:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Ujjwala 2013-07-04 12:15:06 UTC
Description of problem:
On the windows client, SMB mounted with gluster volume, the file permissions cannot be changed.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a Samba-VFS share for the gluster volume in the /etc/samba/smb.conf file.
2. Map the share on the windows client. Create some files.
3. Right click on the file -> Properties -> click on Security and try to edit the permissions of the file. The permission does not change and there is no error message.

Actual results:

Expected results:
The file permissions should be changed.

Additional info:

Comment 3 Ujjwala 2013-08-01 07:21:18 UTC
Changing the permissions on the folder from windows client is still not working.
Tested it on samba-glusterfs-3.6.9-156.1

Comment 4 Christopher R. Hertel 2013-08-15 00:21:37 UTC
Also impacting our ability to change ACL values from a Windows client:

BZ 989435 allows the permissions to be changed, but does not show the changed permissions because the old values are still in the stat cache.  989435 is in the VERIFIED state, so the fix should be available in the latest build.

Comment 5 surabhi 2013-08-16 12:42:35 UTC
verified with samba-glusterfs-3.6.9-159.1.el6rhs.x86_64

The ACL permissions are working fine.Able to change the permissions.

Comment 7 Scott Haines 2013-09-23 22:29:50 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.