<HTML dir=ltr><HEAD><TITLE>Re: [Lustre-discuss] 1.6.3 -> 1.6.4.2 upgrade</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText91151 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>I asked the same question a while back, and although I was never given a 100% guarantee (they only test between major and minor increments, not across multiple minor increments), the bottom line was that it should work and it did (from 1.6.0.1 -> 1.6.3 without issue). Basically, just install and reboot.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Ron Jerome</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>National Research Council Canada.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> lustre-discuss-bounces@lists.lustre.org on behalf of Charles Taylor<BR><B>Sent:</B> Sun 2/17/2008 7:04 PM<BR><B>To:</B> Lustre-discuss<BR><B>Subject:</B> Re: [Lustre-discuss] 1.6.3 -> 1.6.4.2 upgrade<BR></FONT><BR></DIV>
<DIV><BR>
<P><FONT size=2>Turns out that the client upgrade worked just fine. I had not <BR>noticed that the ko2iblnd module was not in place.<BR><BR>I'm still wondering if I need to do anything special with regard to <BR>upgrading the MGS/MDS and OSSs. I'm hoping to just dump the <BR>software in place and reboot with live clients. Seems kind of <BR>risky, but hey, the docs say you can do it for 1.4 -> 1.6.3 so going <BR>from 1.6.3 -> 1.6.4.2 ought to be a no-brainer, right? :)<BR><BR>Charlie Taylor<BR>UF HPC Center<BR><BR>On Feb 17, 2008, at 3:44 PM, Charles Taylor wrote:<BR><BR>><BR>><BR>> Just updated a single client from 1.6.3 to 1.6.4.2. The<BR>> documentation seems to indicate that an upgraded client should still<BR>> be able to mount the file system from a non-upgraded MGSMDT. The<BR>> documentation appears to be referring to a 1.4 to 1.6 upgrade but I<BR>> made the leap that similar things would apply to 1.6.3 -> 1.6.4.2.<BR>><BR>> As I said, the servers are still running 1.6.3 and have not been<BR>> touched. The client is upgraded to 1.6.4.2. When I try to mount<BR>> the file system I get...<BR>><BR>> Is the MGS specification correct?<BR>> Is the filesystem name correct?<BR>> If upgrading, is the copied client log valid? (see upgrade docs)<BR>><BR>> I've double-checked the first two but I have no idea what the third<BR>> item refers to. The docs doc about using tunefs to manually copy<BR>> client config logs when upgrading an MGS/MDS but they seem to<BR>> indicate that the only issue on the client one needs to worry about<BR>> is the form of the mount command. In going from 1.6.3 to 1.6.4.2,<BR>> that should not be an issue.<BR>> Have I missed a step? Do I need to do something to tell the MGS/MDS<BR>> that the client has been upgraded?<BR>><BR>> Is there newer documentation for going from 1.6.3 to 1.6.4.2? I<BR>> was hoping that I could just upgrade the software on the MGS/MDS and<BR>> OSS (in that order) and restart? Is that not the case?<BR>><BR>> Thanks,<BR>><BR>> charlie taylor<BR>> uf hpc center<BR>> _______________________________________________<BR>> Lustre-discuss mailing list<BR>> Lustre-discuss@lists.lustre.org<BR>> <A href="http://lists.lustre.org/mailman/listinfo/lustre-discuss">http://lists.lustre.org/mailman/listinfo/lustre-discuss</A><BR><BR>_______________________________________________<BR>Lustre-discuss mailing list<BR>Lustre-discuss@lists.lustre.org<BR><A href="http://lists.lustre.org/mailman/listinfo/lustre-discuss">http://lists.lustre.org/mailman/listinfo/lustre-discuss</A><BR></FONT></P></DIV></BODY></HTML>