[Lustre-discuss] upgrade to 1.8.4 and test fallback to 220.127.116.11
Ms. Megan Larko
dobsonunit at gmail.com
Mon Sep 27 09:31:53 PDT 2010
I performed an upgrade of our Lustre file system and corresponding
SuSE kernel. The Lustre upgrade went well. After the upgrade from
18.104.22.168 to 1.8.4 I was able to mount my Lustre volumes. The data was
fine. The quotas started on mount via the lustre params on the MDT
I attempted to add a new lustre tuning parameter to my system (I
wanted to add the *t.group_upcall=NONE.) While the Lustre 1.8.4 read
the 22.214.171.124 tuning parameters without issue and I could add to the
parameters under 1.8.4 without issue, if I tried to change a parameter
requiring that I use the --writeconf option, I learned I had to change
all the parameters from the 126.96.36.199 syntax to the 1.8.4 syntax.
(EXAMPLE: "failover.node" string became "failnode") Okay. This I
can do, BUT...
If I have to revert to 188.8.131.52 (due to a security flaw in the linux
kernel or something...) am I correct in assuming that the lustre 1.8.4
parameter strings would not be understood by the 184.108.40.206 lustre system
(can't have s/w reading into the future, right? Smile)? If that is
the case, then I should not change my lustre 220.127.116.11 parameters into
the newer 1.8.4 strings until I am certain I won't have to revert
back, or be prepared to do a full --writeconf of all *Ts to use the
older 18.104.22.168 strings after going back to the previous kernel
containing the lustre 22.214.171.124 files.
Am I correct on this understanding?
More information about the lustre-discuss