[LU-8421] setstripe -i needs to work in a deterministic way Created: 20/Jul/16 Updated: 30/Jan/22 Resolved: 30/Jan/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Gary Hagensen (Inactive) | Assignee: | WC Triage |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
The expectation for using -i in setstripe (the starting index) is that it either would start at the index and then balance across OSSes or go in index order. It currently appears to go in mount order which can be somewhat random and the order is not able to be determined by a user. |
| Comments |
| Comment by Oleg Drokin [ 21/Jul/16 ] |
|
I don;t think we have any guarantees about that anywhere? Basically as long as there's no need to trigger QoS we pick some order of OSTs - likely the one we have them in internally which I would expect to be index order, but it could be mount order too after all. |