[Lustre-devel] Stripe offset default
eeb at whamcloud.com
Tue Nov 23 09:20:58 PST 2010
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
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.
P.S. Do people also agree that setting user/group/ACL permissions on
OST pools would be a Good Thing?
CTO Whamcloud, Inc.
More information about the lustre-devel