From: nailman23@gmail.com
To: xfs@oss.sgi.com
Subject: XFS and Extended ACLs
Date: Tue, 29 Jun 2010 14:21:42 +0000 [thread overview]
Message-ID: <001636458d40cae4e1048a2bf4e9@google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1332 bytes --]
Hi All,
I have an issue with extended ACLs. The situation is as follows:
1) There are two users (UserA and UserB)
2) They belong to the same group (users)
3) The SAMBA share called "test" has user access enabled for UserA and UserB
4) The UserA creates test.docx file on the "test" share and he becomes the
owner of the file.
5) Then UserB edits the test.docx file and save changes. After that UserB
becomes the owner. It is not an issue because when editing the file Word
creates new temporary file and then, during saving, overwrites the original
file. The issue is when you check ACLs entry you will see that UserA has
his own ACLs entries, although he already belongs to the "users" groups.
This occurs when the share has XFS file system in the bottom.
Then I have created an ext3 file system on the logical volume and after
performing all steps, the UserB was owner of the file, but the UserA was no
longer listed in ACLs entries.
It seems the issue comes from XFS and the way as the XFS handles the ACLs
permissions.
The smb.conf is exactly the same in both cases so I do not believe it is
SAMBA issue, but if you want I can send the smb.conf file.
Do you know if there is way I could overcome this, in other words, that XFS
would behave in the same manner as ie ext3.
Thank you in advance.
Slawek
[-- Attachment #1.2: Type: text/html, Size: 1449 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-06-29 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 14:21 nailman23 [this message]
2010-06-29 23:15 ` XFS and Extended ACLs Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=001636458d40cae4e1048a2bf4e9@google.com \
--to=nailman23@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox