From: Eric Barton <eeb@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Stripe offset default
Date: Tue, 23 Nov 2010 17:20:58 -0000 [thread overview]
Message-ID: <016b01cb8b32$cc3a9c90$64afd5b0$@com> (raw)
Nick Cardo at NERSC mentioned at the LUG, and again when I chatted
with him at SC10, that setting the default stripe offset is positively
dangerous. I think he has a point.
Setting file layout precisely can be essential for applications that
know precisely what they're doing and want to control how aggregate
OST load is balanced. But the default file layout is another matter
entirely. Setting the default to a fixed layout, or even just a fixed
starting OST has got to be the most direct path to achieving OST load
imbalance.
I believe, now that lfs setstripe uses options rather than positional
parameters, that the risk of unintentional errors is much less. But
that still leaves the filesystem vulnerable to na?ve or malicious
users. So I propose that we should continue to check permissions
normally when setting the default stripe _count_, but restrict the
ability to set a specific default stripe _offset_ to the superuser.
Thoughts?
P.S. Do people also agree that setting user/group/ACL permissions on
OST pools would be a Good Thing?
Cheers,
Eric
Eric Barton
CTO Whamcloud, Inc.
next reply other threads:[~2010-11-23 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 17:20 Eric Barton [this message]
2010-11-23 19:49 ` [Lustre-devel] Stripe offset default 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 ` [Lustre-devel] OST pool administration (was RE: Stripe offset default) Eric Barton
2010-11-24 15:09 ` 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='016b01cb8b32$cc3a9c90$64afd5b0$@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.