[LU-8885] zconf_mount_clients() defect

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.10.1, Lustre 2.11.0
• Affects Version/s: Lustre 2.5.1
• Severity: 3
• Assignee: WC Triage
• Reporter: Arshad Hussain

Description

"zconf_mount_clients()" does not check that lustre fs is mounted on $mnt,
it just checks "mount | grep -c $mnt".
In case if nfs client is mounted on $mnt zconf_mount_clients() does not try to mount lustre client at all.

Starting client redpill-client02,redpill-client03,redpill-client04,redpill-client05,redpill-client06,redpill-client07,redpill-client08.ext:  -o user_xattr,flock 172.18.1.3@o2ib:/fs1 /mnt/fs1
Started clients redpill-client02,redpill-client03,redpill-client04,redpill-client05,redpill-client06,redpill-client07,redpill-client08.ext: 
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)
172.16.200.1:/mnt/fs1 on /mnt/fs1 type nfs (rw,nfsvers=3,addr=172.16.200.1)