Hi David,<br><br>You need to umount your OSTs and MDTs and run tunefs.lustre --writeconf /dev/<lustre device> on all Lustre OSTs and MDTs This will force the lustre targets to fetch new configuration next time they are mounted. The order of mounting is: MGT -> MDT -> OSTs<br>
<br>Best regards,<br><br>Wojciech <br><br><br><br><div class="gmail_quote">On 17 August 2010 18:19, David Noriega <span dir="ltr"><<a href="mailto:tsk133@my.utsa.edu">tsk133@my.utsa.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Oppps some how I changed the target name of all OSTs to lustre-OST0000<br>
and trying to mount any other ost fails. I've gone and found the 'More<br>
Complicated Configuration' section which details the usage of<br>
--mgsnode=nid1,nid2 and so using this I think I'll just reformat.<br>
<div><div></div><div class="h5"><br>
On Tue, Aug 17, 2010 at 11:26 AM, David Noriega <<a href="mailto:tsk133@my.utsa.edu">tsk133@my.utsa.edu</a>> wrote:<br>
> Some info:<br>
> MDS/MGS 192.168.5.104<br>
> Passive failover MDS/MGS 192.168.5.105<br>
> OSS1 192.168.5.100<br>
> OSS2 192.168.5.101<br>
><br>
> I've got some more questions about setting up failover. Besides having<br>
> heartbeat setup, what about using tunefs.lustre to set options?<br>
><br>
> On the MDS/MGS I set the following options<br>
> tunefs.lustre --failnode=192.168.5.105 /dev/lustre-mdt-dg/lv1<br>
> Heartbeat works just fine, can mount on the primary node and then<br>
> failover to the other and back.<br>
><br>
> Now on the OSSs things get a bit more confusing. Reading these two blog posts:<br>
> <a href="http://mergingbusinessandit.blogspot.com/2008/12/implementing-lustre-failover.html" target="_blank">http://mergingbusinessandit.blogspot.com/2008/12/implementing-lustre-failover.html</a><br>
> <a href="http://jermen.posterous.com/lustre-mds-failover" target="_blank">http://jermen.posterous.com/lustre-mds-failover</a><br>
><br>
> From these I tried these options:<br>
> tunefs.lustre --erase-params --mgsnode=192.168.5.104@tcp0<br>
> --mgsnode=192.168.5.105@tcp0 --failover=192.168.5.101@tcp0<br>
> -write-params /dev/lustre-ost1-dg1/lv1<br>
><br>
> I ran that for all for OSTs, changing the failover option on the last<br>
> two OSTs to point OSS1 while the first two point to OST2.<br>
><br>
> My understanding is that you mount the OSTs first, then the MDS, but<br>
> the OSTs are failing to mount. Are all these options needed? Or is<br>
> simply specifying the primary MDS is enough for it to find out about<br>
> the second MDS?<br>
><br>
> David<br>
><br>
> On Mon, Aug 16, 2010 at 2:14 PM, Kevin Van Maren<br>
> <<a href="mailto:kevin.van.maren@oracle.com">kevin.van.maren@oracle.com</a>> wrote:<br>
>> David Noriega wrote:<br>
>>><br>
>>> Ok I've gotten heartbeat setup with the two OSSs, but I do have a<br>
>>> question that isn't stated in the documentation. Shouldn't the lustre<br>
>>> mounts be removed from fstab once they are given to heartbeat since<br>
>>> when it comes online, it will mount the resources, correct?<br>
>>><br>
>>> David<br>
>>><br>
>><br>
>><br>
>> Yes: on the servers, they must be not there or "noauto". Once you start<br>
>> running heartbeat,<br>
>> you have given control of the resource away, and must not mount/umount it<br>
>> yourself<br>
>> (unless you stop heartbeat on both nodes in the HA pair to get control<br>
>> back).<br>
>><br>
>> Kevin<br>
>><br>
>><br>
><br>
><br>
><br>
> --<br>
> Personally, I liked the university. They gave us money and facilities,<br>
> we didn't have to produce anything! You've never been out of college!<br>
> You don't know what it's like out there! I've worked in the private<br>
> sector. They expect results. -Ray Ghostbusters<br>
><br>
<br>
<br>
<br>
--<br>
Personally, I liked the university. They gave us money and facilities,<br>
we didn't have to produce anything! You've never been out of college!<br>
You don't know what it's like out there! I've worked in the private<br>
sector. They expect results. -Ray Ghostbusters<br>
_______________________________________________<br>
Lustre-discuss mailing list<br>
<a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss" target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Wojciech Turek<br><br>Senior System Architect<br><br>High Performance Computing Service<br>University of Cambridge<br>Email: <a href="mailto:wjt27@cam.ac.uk" target="_blank">wjt27@cam.ac.uk</a><br>
Tel: (+)44 1223 763517 <br>