[LU-14480] Setting specific OST's under pool failed with error message "invalid argument" Created: 02/Mar/21 Updated: 30/Mar/22 Resolved: 22/Mar/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.15.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Vitaly Fertman | Assignee: | Vitaly Fertman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Severity: | 3 | ||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||
| Description |
|
the Error appears if the specific OST is not in the pool. at the same time, only the first OST is checked. the regular setstripe and overstripe's -C option works fine and the same way - they allocate OSTs within the given pool starting with the -i first OST. if the starting index is out of the pool, it is always enough to check only the first ost index in lod_qos_parse_config() ->lod_check_index_in_pool() however the -o option gives a new opportunity to list all the OSTs we want to place stripes to. and checking only the 1st index is not enough - as the result we may get an error or succeed depending on the 1st index only. [root@vm71 wc-main]# mkdir /mnt/lustre/d1 the given OST list should have a priority over the pool. |
| Comments |
| Comment by Gerrit Updater [ 02/Mar/21 ] |
|
Vitaly Fertman (vitaly.fertman@hpe.com) uploaded a new patch: https://review.whamcloud.com/41815 |
| Comment by Gerrit Updater [ 22/Mar/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/41815/ |
| Comment by Peter Jones [ 22/Mar/21 ] |
|
Landed for 2.15 |
| Comment by Gerrit Updater [ 28/Jan/22 ] |
|
"Etienne AUJAMES <eaujames@ddn.com>" uploaded a new patch: https://review.whamcloud.com/46362 |