On Sat, May 7, 2016 at 9:53 PM, Eric Eastman <eric.eastman@xxxxxxxxxxxxxx> wrote: > On Fri, May 6, 2016 at 2:14 PM, Eric Eastman > <eric.eastman@xxxxxxxxxxxxxx> wrote: > >> As it should be working, I will increase the logging level in my >> smb.conf file and see what info I can get out of the logs, and report back. > > Setting the log level = 20 in my smb.conf file, and trying to add an > additional user to a directory on the Windows 2012 server, that has > mounted the share using a fuse mount to a Ceph file system shows the > error: "Operation not supported" in the smbd log file: > > [2016/05/07 23:41:19.213997, 10, pid=2823630, effective(2000501, > 2000514), real(2000501, 0)] > ../source3/modules/vfs_posixacl.c:92(posixacl_sys_acl_set_file) > Calling acl_set_file: New folder (4), 0 > [2016/05/07 23:41:19.214170, 10, pid=2823630, effective(2000501, > 2000514), real(2000501, 0)] > ../source3/modules/vfs_posixacl.c:111(posixacl_sys_acl_set_file) > acl_set_file failed: Operation not supported > > A simple test of setting an ACL from the command line to a fuse > mounted Ceph file system also fails: > # mkdir /cephfsFUSE/x > # setfacl -m d:o:rw /cephfsFUSE/x > setfacl: /cephfsFUSE/x: Operation not supported > > The same test to the same Ceph file system using the kernel mount > method works. > > Is there some option in my ceph.conf file or on the mount line that > needs to be used to support setting ACLs on a fuse mounted Ceph file > system? A quick check of the man page doesn't tell me what setfacl is doing, but I imagine this is another oddity of using FUSE filesystems. Judging by https://sourceforge.net/p/fuse/mailman/message/23787505/ there's some superblock flag that needs to be set in order for the VFS to allow ACLs. I'm not sure offhand if that's something that FUSE will let us do or not; please create a tracker ticket and somebody will get to it. -Greg _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |