[gpfsug-discuss] default owner and group for POSIX ACLs

Wed Oct 16 05:41:39 BST 2019

Hi

In case you want to review with ls -l the POSIX permissions, please put 
the relevant permissions on the SMB share, and add CREATOROWNER & 
CREATETORGROUP.
Than ls -l will show you the owner + group + everyone permissions.

Regards

Yaron Daniel
 94 Em Ha'Moshavot Rd

Storage Architect – IL Lab Services (Storage)
 Petach Tiqva, 49527
IBM Global Markets, Systems HW Sales
 Israel

Phone:
+972-3-916-5672

Fax:
+972-3-916-5672

Mobile:
+972-52-8395593

e-mail:
yard at il.ibm.com

Webex:            https://ibm.webex.com/meet/yard
IBM Israel

From:   Jonathan Buzzard <jonathan.buzzard at strath.ac.uk>
To:     "gpfsug-discuss at spectrumscale.org" 
<gpfsug-discuss at spectrumscale.org>
Date:   15/10/2019 23:34
Subject:        [EXTERNAL] Re: [gpfsug-discuss] default owner and group 
for POSIX ACLs
Sent by:        gpfsug-discuss-bounces at spectrumscale.org

On 15/10/2019 17:15, Paul Ward wrote:

[SNIP]

>> ...I am not sure why you need POSIX ACL's if you are running Linux...
>  From what I have recently read...
> 
https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.adm.doc/bl1adm_admnfsaclg.htm

> "Linux does not allow a file system to be NFS V4 exported unless it 
supports POSIX ACLs."
> 

Only if you are using the inbuilt kernel NFS server, which IMHO is awful 
from a management perspective. That is you have zero visibility into 
what the hell it is doing when it all goes pear shaped unless you break 
out dtrace. I am not sure that using  dtrace on a production service to 
find out what is going on is "best practice". It also in my experience 
stops you cleanly shutting down most of the time. The sooner it gets 
removed from the kernel the better IMHO.

If you are using protocol nodes which is the only supported option as 
far as I am aware then that does not apply. I would imagined if you are 
rolling your own Ganesha NFS server it won't matter either.

Checking the code of the FSAL in Ganesha shows functions for converting 
between GPFS ACL's and the ACL format as used by Ganesha. My 
understanding was one of the drivers for using Ganesha as an NFS server 
with GPFS was you can write a FSAL to do just that, in the same way as 
on Samba you load the vfs_gpfs module, unless you are into self 
flagellation I guess.

JAB.

-- 
Jonathan A. Buzzard                         Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=Bn1XE9uK2a9CZQ8qKnJE3Q&m=b8w1GtIuT4M2ayhd-sZvIeIGVRrqM7QoXlh1KVj4Zq4&s=huFx7k3Vx10aZ-7AVq1HSVo825JPWVdFaEu3G3Dh-78&e= 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1114 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3847 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0016.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4266 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0017.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3747 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0018.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3793 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0019.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4301 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0020.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3739 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0021.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3855 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0022.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4338 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191016/dd45c2ed/attachment-0023.jpe>