Minor 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!
Attachments
Issue Links
Activity
| Link | New: This issue is related to EX-11340 [ EX-11340 ] |
| Labels | Original: easy | New: easy usability |
| Description |
Original:
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 "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! |
New:
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! |
| Description |
Original:
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 "setstripe -i" functionality on a per-filesystem basis. Andreas summed it up pretty well with: "as for blocking users from being able to use "setstripe -i", we could add feature with a /proc tunable on the MDS that prevents regular users from doing this, but it would be off by default" Thanks! |
New:
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 "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! |
| Description |
Original:
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 customer has requested the ability to disable the "setstripe -i" functionality on a per-filesystem basis. Andreas summed it up pretty well with: "as for blocking users from being able to use "setstripe -i", we could add feature with a /proc tunable on the MDS that prevents regular users from doing this, but it would be off by default" Thanks! |
New:
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 "setstripe -i" functionality on a per-filesystem basis. Andreas summed it up pretty well with: "as for blocking users from being able to use "setstripe -i", we could add feature with a /proc tunable on the MDS that prevents regular users from doing this, but it would be off by default" Thanks! |