[LU-6689] Requesting a tunable that prevents regular users from setting the initial OST

• Type: New Feature
• Resolution: Unresolved
• Priority: Minor
• Labels: easy usability
• Assignee: WC Triage
• Reporter: Brett Lee (Inactive)

Description

The ability to explicitly define the initial OST for a new file has been misused by some end users. While we all agree that removing this feature should not be the solution, at least one user has requested the ability to disable the lfs setstripe -i functionality on a per-filesystem basis.

One option is to block users from being able to use lfs setstripe -i by adding a /proc tunable on the MDS that prevents regular users from doing this, but it would be off by default.

Thanks!

Issue Links

• is related to: LU-9162 Option to set max stripe count per filesystem
• is related to: LU-17628 add option to restrict lfs setstripe

Comments

[Andreas Dilger]

This is at least partly implemented by patch https://review.whamcloud.com/54341 ("LU-17628 lfs: add lfs_setstripe admin restrict"), which prevents users from setting any parameters with "lfs setstripe". However, that is a "soft" restriction that can be overridden by application libraries, while this should probably be implemented as an RBAC control on a nodemap.