Hi all! I have Samba 4.0.0alpha17 installed, running as a PDC for my small home network. ?Everything works great, but I'm noticing something odd. ?When a user creates a file, it's created with a non-existent owner on the filesystem. ?The group is OK. The problem is that when I set ACL's from a Windows computer, the files with that owner can't be changed (i.e., Windows gives a 'retry/continue/cancel" dialog). ?If I change those files to root:users, I can set ACL's on them all day long. I've searched all over and can't find out any clues as to why this is happening, or how to correct it. My questions: - What underlying filesystem permissions, owner and group should I set for files/directories in a Samba share? - Should I/Can I force the owner/group and permissions on newly created files? - Why are new files created with a non-existent user in the first place? My installation: - Ubuntu 11.10 (server) - Underlying filesystem is a mix of EXT3 and EXT4 (EXT3 FS has xattrs enabled and working) - Not using UNIX users; the users are all in the internal Samba database - Samba runs as root - My smb.conf file is using a bare minimum of options; just enough to define shares and set some service information Thanks for your help. Brantley
> > > The problem is that when I set ACL's from a Windows computer, the > files with that owner can't be changed (i.e., Windows gives a > 'retry/continue/cancel" dialog). If I change those files to > root:users, I can set ACL's on them all day long.You likely don't have ACL's enabled on the filesystem that samba is sharing. You can check with sudo tune2fs -l /dev/vg_lillie/lv_root | grep option replacing your disk into that command. You should see something like Default mount options: user_xattr acl If not, you should enable the filesystem ACL using tune2fs, then reboot your machine. tune2fs -o acl /dev/sda1 Sincerely, William Brown Research & Teaching, Technology Services The University of Adelaide, AUSTRALIA 5005 CRICOS Provider Number 00123M ----------------------------------------------------------------------------- IMPORTANT: This message may contain confidential or legally privileged information. If you think it was sent to you by mistake, please delete all copies and advise the sender. For the purposes of the SPAM Act 2003, this email is authorised by The University of Adelaide. pgp.mit.edu http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x3C0AC6DAB2F928A2 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.samba.org/pipermail/samba/attachments/20120209/934cd4e3/attachment.pgp>
Apparently Analagous Threads
- source definition for R_NilValue/return from TYPEOF(R_NilValue)
- Resize journal on root filesystem
- tune2fs: Filesystem has unsupported feature(s) while trying to open
- tune2fs: Filesystem has unsupported feature(s) while trying to open
- Problem with root filesystem