[LU-12473] pool_list by path incorrectly prints path as pool prefix Created: 25/Jun/19 Updated: 05/Aug/20 Resolved: 12/Jul/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.0, Lustre 2.12.2 |
| Fix Version/s: | Lustre 2.13.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | CEA | Assignee: | Dominique Martinet (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
The lfs/lctl pool_list command incorrectly re-uses the path as pool prefix when printing pools, e.g. with a fresh llmount:
[root@vm0 ~]# lctl pool_new lustre.foo lfs Pool lustre.foo created [root@vm0 ~]# lctl pool_list /mnt/lustre Pools from /mnt/lustre: /mnt/lustre.foo /mnt/lustre.foo is not a valid pool name and scripts looking at this output to use directly with lfs setstripe -p will now fail On old 2.7 at least, this would correctly print lustre.foo instead |
| Comments |
| Comment by Gerrit Updater [ 25/Jun/19 ] |
|
Dominique Martinet (dominique.martinet@cea.fr) uploaded a new patch: https://review.whamcloud.com/35320 |
| Comment by Peter Jones [ 25/Jun/19 ] |
|
Thanks Dominique! |
| Comment by Gerrit Updater [ 12/Jul/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/35320/ |
| Comment by Peter Jones [ 12/Jul/19 ] |
|
Landed for 2.13 |