From: Eric Barton <eeb@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] OST pool administration (was RE: Stripe offset default)
Date: Wed, 24 Nov 2010 13:31:50 -0000 [thread overview]
Message-ID: <01b501cb8bdb$f3ff3ac0$dbfdb040$@com> (raw)
In-Reply-To: <4FE51862-3264-4248-948F-CF70C56FD8AD@xyratex.com>
Peter,
> The proposal for acl / Group / users violates Posix, and may lead
> to results users don't expect. Sgid directories and inheritance
> on ACLs are safer I think.
This should probably be in a separate thread since I was trying to make
a case for improving the administration storage pools (the classic
gold/silver/bronze scenarios) which is really different from the default
file layout issue.
If the default layout in a directory creates files in the "gold" OST
pool but the user has no permissions for that pool, then returning
EPERM on file creation would potentially be inconsistent with the
permissions on the directory itself. Is this what you meant by being
inconsistent with Posix? If so, I'm afraid I don't follow the point
about sgid.
I guess using per-pool quotas rather than permissions might be more
natural. I'd be interested to hear people's opinions...
Cheers,
Eric
next prev parent reply other threads:[~2010-11-24 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 17:20 [Lustre-devel] Stripe offset default Eric Barton
2010-11-23 19:49 ` Christopher J. Morrone
2010-11-23 21:19 ` Andreas Dilger
2010-11-23 22:59 ` Christopher J. Morrone
2010-11-23 20:21 ` Ashley Pittman
2010-11-23 20:50 ` Peter Braam
2010-11-23 21:47 ` Andreas Dilger
2010-11-24 13:31 ` Eric Barton [this message]
2010-11-24 15:09 ` [Lustre-devel] OST pool administration (was RE: Stripe offset default) Peter Braam
2010-11-23 21:40 ` [Lustre-devel] Stripe offset default Andreas Dilger
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='01b501cb8bdb$f3ff3ac0$dbfdb040$@com' \
--to=eeb@whamcloud.com \
--cc=lustre-devel@lists.lustre.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.