<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
Hello,<br>
<br>
thank you very much for the answer. We are at least happy that
it not caused by our setup.<br>
It is pitty that lustre does not work as it should according to its
documentation.<br>
The problem is that a directory permissions created by a user
depends on umask setting of the user. <br>
Probably there is no way not to allow users change their umask from
some fixed properly tunned value. <br>
For now we have some workaround, but we would prefer as it is described
in docs.<br>
<br>
Will this be fixed in the further lustre versions, or this is how it
should work?<br>
<br>
Thank you. Gizo<br>
<br>
<br>
<br>
<br>
On 05/19/2010 08:03 PM, Giacinto Donvito wrote:
<blockquote
cite="mid:AANLkTimHJrgVkl_XrBDLMCpSnFxHsmtbdJ0D1Ko1Mn48@mail.gmail.com"
type="cite">Hi Gizo,
<div><br>
</div>
<div>we have lustre 1.8.x in production with ACLs enabled and we use
them a lot indeed.</div>
<div><br>
</div>
<div>I'm experiencing the same behaviour that you mention here.</div>
<div><br>
</div>
<div>Why is this a problem? </div>
<meta charset="utf-8">
<div><br>
</div>
<div>Cheers,</div>
<div>Giacinto</div>
<div><br clear="all">
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
Giacinto Donvito LIBI -- EGEE2 SA1 INFN - Bari ITALY<br>
------------------------------------------------------------------<br>
<a moz-do-not-send="true" href="mailto:giacinto.donvito@ba.infn.it">giacinto.donvito@ba.infn.it</a>
| GTalk/GMail: <a moz-do-not-send="true"
href="mailto:donvito.giacinto@gmail.com">donvito.giacinto@gmail.com</a><br>
tel. +39 080 5443244 Fax +39 0805442470 VOIP: +41225481596 |
MSN: <a moz-do-not-send="true"
href="mailto:donvito.giacinto@hotmail.it">donvito.giacinto@hotmail.it</a><br>
Skype: giacinto_it | AIM/iChat: gdonvito1 | Yahoo: eric1_it <br>
------------------------------------------------------------------<br>
"A simple design always takes less time to finish than a complex one.<br>
So always do the simplest thing that could possibly work."<br>
Don <a moz-do-not-send="true"
href="mailto:Wells@www.extremeprogramming.org">Wells@www.extremeprogramming.org</a><br>
<br>
<br>
<br>
<div class="gmail_quote">On Wed, May 19, 2010 at 19:57, Gizo Nanava <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:nanava@physik.uni-bonn.de">nanava@physik.uni-bonn.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Hello,<br>
<br>
some time ago i have ask the question about *default* acl problem<br>
is lustre, but have not got any answer yer.<br>
could you please someone give me this one bit of info. it is very simple<br>
if you already have this lustre installed.<br>
we are using it in large prod. site.. and are interested if that is our<br>
fault or not.. Thanks!<br>
<font color="#888888"><br>
GN<br>
</font>
<div>
<div class="h5"><br>
<br>
On 05/14/2010 11:20 AM, Gizo Nanava wrote:<br>
> Hello,<br>
><br>
> on our cluster where we have Scientific Linux 5.4 (64-bit, kernel<br>
> 2.6.18-164.11.1) and Lustre 1.8.2<br>
> we are experiencing problem with setting of default ACLs.<br>
><br>
> According to rules, newly created files and directories in the<br>
> directory with a default ACLs set, get<br>
> permissions of the parent directory, thus ignoring the value of
umask.<br>
> As we have checked this is really the case on Linux with ext3, but
we<br>
> can not make this working in Lustre.<br>
><br>
> Here is an example.<br>
><br>
> On ACL enabled linux (Ubuntu Lucid,32-bit, kernel<br>
> 2.6.32-21-generic-pae):<br>
><br>
> > mkdir noalc<br>
> > mkdir acl<br>
> > setfacl -d --set u::rwx,g::rx,g:atlas:rwx acl<br>
> > getfacl -c acl<br>
> default:user::rwx<br>
> default:group::r-x<br>
> default:group:atlas:rwx<br>
> default:mask::rwx<br>
><br>
> > umask 0777<br>
> > mkdir noacl/dir<br>
> > ls -l noacl<br>
> d--------- 2 root root .... dir<br>
><br>
> > mkdir acl/dir<br>
> > getfacl -a acl/dir<br>
> user::rwx<br>
> group::r-x<br>
> group:atlas:rwx<br>
> mask::rwx<br>
><br>
> So, here everything is okay.<br>
><br>
> But, on Lustre the last command above looks as follows<br>
> > getfacl --access --omit-header acl/dir<br>
> user::---<br>
> group::r-x #effective:---<br>
> group:atlas:rwx #effective:---<br>
> mask::---<br>
><br>
> So, the value of umask is not ignored.<br>
><br>
> Does somebody else experience the same problem?<br>
> What could be wrong in our lustre setup? As usually ACL on MDS is<br>
> enabled by mount -o acl..<br>
> The same problem is in lustre 1.6.6. Thank you very much for any
help!<br>
><br>
> Best wishes, Gizo Nanava<br>
><br>
<br>
_______________________________________________<br>
Lustre-discuss mailing list<br>
<a moz-do-not-send="true"
href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
<a moz-do-not-send="true"
href="http://lists.lustre.org/mailman/listinfo/lustre-discuss"
target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>