Just updated a single client from 1.6.3 to 1.6.4.2. The documentation seems to indicate that an upgraded client should still be able to mount the file system from a non-upgraded MGSMDT. The documentation appears to be referring to a 1.4 to 1.6 upgrade but I made the leap that similar things would apply to 1.6.3 -> 1.6.4.2. As I said, the servers are still running 1.6.3 and have not been touched. The client is upgraded to 1.6.4.2. When I try to mount the file system I get... Is the MGS specification correct? Is the filesystem name correct? If upgrading, is the copied client log valid? (see upgrade docs) I''ve double-checked the first two but I have no idea what the third item refers to. The docs doc about using tunefs to manually copy client config logs when upgrading an MGS/MDS but they seem to indicate that the only issue on the client one needs to worry about is the form of the mount command. In going from 1.6.3 to 1.6.4.2, that should not be an issue. Have I missed a step? Do I need to do something to tell the MGS/MDS that the client has been upgraded? Is there newer documentation for going from 1.6.3 to 1.6.4.2? I was hoping that I could just upgrade the software on the MGS/MDS and OSS (in that order) and restart? Is that not the case? Thanks, charlie taylor uf hpc center
Turns out that the client upgrade worked just fine. I had not noticed that the ko2iblnd module was not in place. I''m still wondering if I need to do anything special with regard to upgrading the MGS/MDS and OSSs. I''m hoping to just dump the software in place and reboot with live clients. Seems kind of risky, but hey, the docs say you can do it for 1.4 -> 1.6.3 so going from 1.6.3 -> 1.6.4.2 ought to be a no-brainer, right? :) Charlie Taylor UF HPC Center On Feb 17, 2008, at 3:44 PM, Charles Taylor wrote:> > > Just updated a single client from 1.6.3 to 1.6.4.2. The > documentation seems to indicate that an upgraded client should still > be able to mount the file system from a non-upgraded MGSMDT. The > documentation appears to be referring to a 1.4 to 1.6 upgrade but I > made the leap that similar things would apply to 1.6.3 -> 1.6.4.2. > > As I said, the servers are still running 1.6.3 and have not been > touched. The client is upgraded to 1.6.4.2. When I try to mount > the file system I get... > > Is the MGS specification correct? > Is the filesystem name correct? > If upgrading, is the copied client log valid? (see upgrade docs) > > I''ve double-checked the first two but I have no idea what the third > item refers to. The docs doc about using tunefs to manually copy > client config logs when upgrading an MGS/MDS but they seem to > indicate that the only issue on the client one needs to worry about > is the form of the mount command. In going from 1.6.3 to 1.6.4.2, > that should not be an issue. > Have I missed a step? Do I need to do something to tell the MGS/MDS > that the client has been upgraded? > > Is there newer documentation for going from 1.6.3 to 1.6.4.2? I > was hoping that I could just upgrade the software on the MGS/MDS and > OSS (in that order) and restart? Is that not the case? > > Thanks, > > charlie taylor > uf hpc center > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
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. Ron Jerome National Research Council Canada. ________________________________ From: lustre-discuss-bounces at lists.lustre.org on behalf of Charles Taylor Sent: Sun 2/17/2008 7:04 PM To: Lustre-discuss Subject: Re: [Lustre-discuss] 1.6.3 -> 1.6.4.2 upgrade Turns out that the client upgrade worked just fine. I had not noticed that the ko2iblnd module was not in place. I''m still wondering if I need to do anything special with regard to upgrading the MGS/MDS and OSSs. I''m hoping to just dump the software in place and reboot with live clients. Seems kind of risky, but hey, the docs say you can do it for 1.4 -> 1.6.3 so going from 1.6.3 -> 1.6.4.2 ought to be a no-brainer, right? :) Charlie Taylor UF HPC Center On Feb 17, 2008, at 3:44 PM, Charles Taylor wrote:> > > Just updated a single client from 1.6.3 to 1.6.4.2. The > documentation seems to indicate that an upgraded client should still > be able to mount the file system from a non-upgraded MGSMDT. The > documentation appears to be referring to a 1.4 to 1.6 upgrade but I > made the leap that similar things would apply to 1.6.3 -> 1.6.4.2. > > As I said, the servers are still running 1.6.3 and have not been > touched. The client is upgraded to 1.6.4.2. When I try to mount > the file system I get... > > Is the MGS specification correct? > Is the filesystem name correct? > If upgrading, is the copied client log valid? (see upgrade docs) > > I''ve double-checked the first two but I have no idea what the third > item refers to. The docs doc about using tunefs to manually copy > client config logs when upgrading an MGS/MDS but they seem to > indicate that the only issue on the client one needs to worry about > is the form of the mount command. In going from 1.6.3 to 1.6.4.2, > that should not be an issue. > Have I missed a step? Do I need to do something to tell the MGS/MDS > that the client has been upgraded? > > Is there newer documentation for going from 1.6.3 to 1.6.4.2? I > was hoping that I could just upgrade the software on the MGS/MDS and > OSS (in that order) and restart? Is that not the case? > > Thanks, > > charlie taylor > uf hpc center > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss_______________________________________________ Lustre-discuss mailing list Lustre-discuss at lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080217/338d3dab/attachment-0002.html