[Lustre-discuss] Problem with write_conf

Roger Spellman Roger.Spellman at terascala.com
Tue Aug 3 13:21:39 PDT 2010


Nathan,

 

Thanks.  That works great.

 

Are there any tricks involved in also making a non-redundant system
redundant at the same time?  E.g. Can I just do:

 

 

MDS#  tunefs.lustre --erase-param --mgsnode=10.2.9.201 at o2ib0
--failnode=10.2.9.202 at o2ib0 /dev/mapper/map0 

OSS#  tunefs.lustre --erase-param --failnode=10.2.9.204 at o2ib0
--mgsnode=10.2.9.201 at o2ib0 --mgsnode=10.2.9.202 at o2ib0 /dev/mapper/map0

 

Is the OSS's NID stored anywhere on the OST?

 

-Roger

 

________________________________

From: Nathan Rutman [mailto:nathan.rutman at oracle.com] 
Sent: Tuesday, August 03, 2010 4:05 PM
To: Roger Spellman
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [Lustre-discuss] Problem with write_conf

 

 

On Aug 3, 2010, at 12:49 PM, Roger Spellman wrote:





If I change the NIDs, and if I don't remove /mnt/mdt/CONFIGS/*-client,
then I get the following when I try mounting a client (note that
10.2.9.1 is the OLD address):

 

mount.lustre: mount 10.2.9.1 at o2ib:/hss2 at /mnt/lustre-hss2 failed:
Cannot send after transport endpoint shutdown

 

Don't mount with the old address :)

This is not contained in the config log; this is the MGS address the
client needs to talk to to GET the config log.  It needs to point to the
current IP of the MGS.  Maybe you've stuck this in /etc/fstab or perhaps
your DNS name resolution of the MGS's common name hasn't been updated. 





 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20100803/5f72f4cf/attachment.htm>


More information about the lustre-discuss mailing list