On 05/31/2018 07:49 PM, Trond Myklebust wrote: > On Thu, 2018-05-31 at 16:53 -0500, Goldwyn Rodrigues wrote: >> >> On 05/31/2018 08:30 AM, Miklos Szeredi wrote: >>> On Thu, May 31, 2018 at 3:10 PM, Trond Myklebust >>> <trondmy@xxxxxxxxxxxxxxx> wrote: >>>>> >>>>> I understand. Ignoring nfs4_acl in overlayfs will have the >>>>> same >>>>> result as adding noacl to the underlying NFS mount. >> >> Adding noacl in NFS client mount has no affect to nfs4_acl. Only if >> you >> add noacl in the underlying filesystem of exported directory in the >> server does the nfs4_acl go away. > > That would also be specific to Linux servers. Sorry, I don't have access to other NFS based servers. Does that mean "noacl" option on NFS client mount has different interpretations for different NFS servers? Or do you mean that nfs4_acl cannot be disabled for other type of servers? > > So if that is your final decision, then why not just state in the > overlayfs manpage that No, that is not my final decision. Neither is it for me to make. I am merely trying to find a way to make writes on overlayfs possible with NFSv4 in the lower layer. -- Goldwyn -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
