[Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

Mike Hanby mhanby at uab.edu
Thu Sep 9 15:17:43 PDT 2010

That's odd, I have and use _netdev for both my Infiniband and GigE clients, both mount successfully.

For IB clients: at o2ib:/lustre    /lustre       lustre  _netdev         0 0

And GigE clients: at tcp:/lustre  /lustre       lustre  _netdev         0 0

-----Original Message-----
From: lustre-discuss-bounces at lists.lustre.org [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of Nirmal Seenu
Sent: Thursday, September 09, 2010 2:58 PM
To: Ken Hornstein
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [Lustre-discuss] Problem with LNET and openibd on Lustre 1.8.4 while rebooting

I guess the trick is to use _netdev as an option in the mount command or the /etc/fstab entry as Andreas mentioned.

I used to have the _netdev option when I was using Lustre over ethernet which made the automounts work correctly and I didn't have the LNET problem.

With infiniband(openibd) the _netdev option doesn't mount lustre correctly and I had to mount lustre from rc.local after the infiniband networks comes up.


On 09/09/2010 02:44 PM, Ken Hornstein wrote:
>> lustre does get unmounted before NFS filesystem as seen in the log message...
>> the problem is due to the fact that LNET is still up when openibd gets
>> removed.
> Huh, I'm wondering how it ever worked "right" before.  Certainly on the systems
> I have at, I always had to have a Lustre start/stop script which did
> a lustre_rmmod as part of the stop sequence.
> --Ken
Lustre-discuss mailing list
Lustre-discuss at lists.lustre.org

More information about the lustre-discuss mailing list