On Wed, 2012-04-25 at 14:35 +0200, Nicolas Ecarnot wrote:
> [Sorry for cross-posting, but I sincerely don't know who's best to answer]
> Using many production Samba file servers on RHEL 5.6 for a while, we are
> now finishing to setup a samba cluster on Ubuntu-server (oneiric) with
> Like on our other samba setups, we are using ACLs and we set up the
> setgid bit on our folders (chmod g+s folder), as well as default ACL.
> The access rights are managed via the basic windows explorer security
> tab and is working nicely.
> But on this new GFS2, I observe that this is not working the same.
> To make it short, the setgid bit gets lost when a user creates a subdir.
> To be precise, here is what I'm observing :
> My folder looks like this :
> root@server:/foo/bar# getfacl .
> # file: .
> # owner: root
> # group: adminsGroup
> # flags: ss-
> * When the user root runs 'mkdir rootDir', this directory correctly gets
> the adequate rights, and it gets the setgid bit (allowing deeper
> inheritance to keep working).
> * When a non-root user belonging to the adminsGroup group runs 'mkdir
> privDir', the directory also gain the same feature as above.
> * When a basic non-root user belonging to the domainUsers group runs
> 'mkdir basicDir', it gets created (the ACL allows it) but the setgid bit
> is *NOT* preserved.
> My tests are showing that with ext3 and ext4, on the same server (and/or
> on other systems), this behavior is different, and that the sgid bit is
> I have added the suiddir flag when mounting the GFS2 partition, but this
> does not improve anything.
> May someone tell me :
> - if this new behavior is faulty or expected?
> - if these mailing-lists are the best place to ask such questions?
> (email@example.com + firstname.lastname@example.org), and if
> needed advice me a better place
> - if this is unexpected, if I should file a bug? (and where)
> Thank you.
It sounds like that might be a bug. If you can open a fedora rawhide
bug, assuming that you are not a Red Hat customer, at Red Hat's
bugzilla, then that will ensure that this doesn't get forgotten. Please
note exactly which kernel version(s) you are using and as much other
detail as possible.
Some other info which may help: Samba is supported on RHEL only in an
active/passive failover configuration, except on RHEL 6.2 and above
where it is supported in active/active.
If you are a Red Hat customer, then please report this issue via our
support team in the first instance.
Also, are you doing the tests when running as the same user on gfs2 and