[LU-1307] Clients having issues mounting Lustre

• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Minor
• Affects Version/s: Lustre 1.8.6
• Environment: Servers: CentOS 5.5; Clients: RHEL 6.0
• Severity: 3
• Assignee: Doug Oucharek (Inactive)
• Reporter: Dennis Nelson

Description

Customer reports that some clients have difficulties mounting Lustre filesystems. Running lustre_rmmod then mount -at lustre seemes to clear up the problem. This is right after a reboot of the system.

[root@dtn1 ~]# mount -at lustre
mount.lustre: mount 10.174.80.40@o2ib2:10.174.80.41@o2ib2:/scratch1 at /scratch1 failed: No such device
Are the lustre modules loaded?
Check /etc/modprobe.conf and /proc/filesystems
Note 'alias lustre llite' should be removed from modprobe.conf
mount.lustre: mount 10.174.80.42@o2ib2:10.174.80.43@o2ib2:/scratch2 at /scratch2 failed: No such device
Are the lustre modules loaded?
Check /etc/modprobe.conf and /proc/filesystems
Note 'alias lustre llite' should be removed from modprobe.conf
[root@dtn1 ~]# lustre_rmmod
[root@dtn1 ~]# mount -at lustre
[root@dtn1 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_dtn1-lv_root
50G 17G 31G 36% /
tmpfs 24G 0 24G 0% /dev/shm
/dev/sda1 485M 52M 408M 12% /boot
10.174.80.40@o2ib2:10.174.80.41@o2ib2:/scratch1
2.5P 288T 2.2P 12% /scratch1
10.174.80.42@o2ib2:10.174.80.43@o2ib2:/scratch2
3.1P 427T 2.7P 14% /scratch2

/etc/fstab:
...
10.174.80.40@o2ib2:10.174.80.41@o2ib2:/scratch1 /scratch1 lustre defaults,flock 0 0
10.174.80.42@o2ib2:10.174.80.43@o2ib2:/scratch2 /scratch2 lustre defaults,flock 0 0

[root@dtn1 ~]# cat /etc/modprobe.d/lustre.conf

1. Lustre module configuration file
   options lnet networks="o2ib2(ib0)"

Also, I have attached /var/log/messages showing the recent boot and the lustre errors reported.

You can see in the log that I ran mount -at lustre at Apr 11 13:14:20.
Then I ran lustre_rmmod and mount -at lustre and it worked.

The customer is asking why this is happening and I do not have an explanation.
I encountered similar issues on other clients after a reboot of the entire system.

Issue Links

• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA