Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.10.0, Lustre 2.12.2
-
3
-
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
The fix is very much straightforward, I'll submit something right away.
Attachments
Issue Links
- is related to
-
LU-12521 print_instance() incorrect if fsname contains a dash
- Resolved