[LU-12733] lctl pool_list on MGS

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.13.0, Lustre 2.12.3
• Severity: 3
• Assignee: WC Triage
• Reporter: Vladimir Saveliev

Description

lctl pool_list does not output pool information.

[root@sl753 ~]# mount | grep lustre -w
/dev/mapper/scientific-root on /usr/sbin/mount.*lustre* type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sdc1 on /mnt/*lustre*-mgs type *lustre* (ro,svname=MGS,nosvc,mgs,osd=osd-ldiskfs,user_xattr,errors=remount-ro)
[root@sl753 ~]# lctl pool_new lustre.p
Pool lustre.p created
[root@sl753 ~]# lctl pool_add lustre.p OST0003
OST lustre-OST0003_UUID added to pool lustre.p
[root@sl753 ~]# lctl pool_list lustre
[root@sl753 ~]# lctl pool_list lustre.p
[root@sl753 ~]# 

Issue Links

• duplicates: LU-11743 lctl pool operations cannot be run on separate MGS system

Comments

[Andreas Dilger]

I see that while patch https://review.whamcloud.com/35804 "LU-11743 utils: allow lctl pool commands on separate MGS" was landed for 2.12.3, the patch https://review.whamcloud.com/36314 "LU-11743 utils: allow lctl pool_list on separate MGS" was only landed for 2.12.4.

[Andreas Dilger]

Nathaniel, it would be useful to get the output from "lctl --device MGS llog_print $fsname-client | grep pool" on the MGS. This is where the MGS-local "lctl pool_list" and other pool commands get their information. I successfully tested "lctl pool_list" on a system (running master) with "/proc/fs/lustre/lov" over-mounted by an empty directory, and verified with strace that the pool lookup failed and read the pool information via ioctl() from the running MGS.

[Nathaniel Clark]

For Lustre 2.12.3 (which has LU-11743)

lctl pool_new|pool_add|pool_remove|pool_destroy all work but lctl pool_list returns nothing on the MGS.

[root@ieel-mds01 ~]# findmnt -t lustre
TARGET   SOURCE   FSTYPE OPTIONS
/mnt/MGS /dev/sdb lustre ro,svname=MGS,nosvc,mgs,osd=osd-ldiskfs,user_xattr,errors=remount-ro
[root@ieel-mds01 ~]# lfs pool_list fs10
[root@ieel-mds01 ~]# 

lctl pool_list works correctly on MDT:

[root@ieel-mds02 ~]# findmnt -t lustre
TARGET            SOURCE   FSTYPE OPTIONS
/mnt/fs10-MDT0000 /dev/sdd lustre ro,svname=fs10-MDT0000,mgsnode=192.168.56.10@tcp:192.168.56.11@tcp,osd=osd-l
[root@ieel-mds02 ~]# lfs pool_list fs10
Pools from fs10:
fs10.pool1

While commands that alter pool look at config logs directly, the pool_list command still tryies to open parse lov, which isn't present on MGS.

[Vladimir Saveliev]

https://review.whamcloud.com/#/c/35895/ from LU-11743 is merged.

[Emoly Liu]

I have a patch to fix this issue at https://review.whamcloud.com/#/c/35895/

[Gerrit Updater]

Vladimir Saveliev ([e-mail]) uploaded a new patch: https://review.whamcloud.com/36104
Subject: LU-12733 utils: lctl pool_list on standalone MGS
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: fc0fc3c55d21e87320de97a3237ce7be7e7de863