[Lustre-discuss] lustre using wrong network

[Lundgren, Andrew]

Look at doing a  --writeconf with tunefs.lustre on all of your OSTs and MDTs.  Then remount them with the correct settings.  

> -----Original Message-----
> From: lustre-discuss-bounces at lists.lustre.org [mailto:lustre-discuss-
> bounces at lists.lustre.org] On Behalf Of Michael Di Domenico
> Sent: Friday, June 19, 2009 6:43 AM
> To: Michael Di Domenico; Lustre-discuss at lists.lustre.org
> Subject: Re: [Lustre-discuss] lustre using wrong network
> 
> On Thu, Jun 18, 2009 at 9:57 PM, Isaac Huang<He.Huang at sun.com> wrote:
> > On Thu, Jun 18, 2009 at 09:51:33PM -0400, Michael Di Domenico wrote:
> >> ......
> >> > But the connection was rejected because the server didn't have
> >> > 192.168.0.248 at tcp as one of its NIDs.
> >> >
> >> > What was your mount command line? What does 'lctl list_nids' say
> on
> >> > the nodes?
> >>
> >> list_nids show the right nid on all the nodes 192.168.1.x at tcp
> >>
> >> 192.168.0.x does exist on all the nodes, but lustre shouldn't be
> >> trying to use it ever
> >
> > Have you changed server NIDs without updating configuration logs with
> > --writeconf?
> 
> By accident the lnet configs came up with the 192.168.0.x config
> because a modprobe setting was wrong.  However, i took the system back
> down and corrected the configuration.
> 
> So i guess the question is how do i clear out the logs if a host comes
> up with a bad NID by accident?
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss