[Lustre-discuss] 1.6.4.2 -> 1.8.0.1 Upgrade Question

[Ms. Megan Larko]

Hello Charlie and others,

I cannot speak for the whys and wherefores, but I know that my upgrade
of an MGS/MDT disk from a smaller Gb volume to a larger Gb volume did
not work until the tunefs.lustre command was run as you have it
referenced below.   In addition, I also had to go to the OSS and for
each OST under the purview of that MDT I had to run the command
"tunefs.lustre --writeconf /dev/{sdX of OST}".   Then everything
worked just fine and dandy (although I did have to run the
tunefs.lustre command on one OST 2x because it would not appear in any
lctl device_list until I ran the tunefs.lustre command on the OST a
second time).

So I don't know why, but it works.

megan


Date: Wed, 22 Jul 2009 17:49:18 -0400
From: Charles Taylor <taylor at hpc.ufl.edu>
Subject: [Lustre-discuss] 1.6.4.2 -> 1.8.0.1 Upgrade Question
To: lustre-discuss <lustre-discuss at lists.lustre.org>
Message-ID: <B9F51ECF-CDCC-43D8-A577-2B61EA58200D at hpc.ufl.edu>
Content-Type: text/plain; charset="us-ascii"


We are about to upgrade our standalone MGS/MDS (no failover) from
1.6.4.2 to 1.8.0.1.    I'm a little confused by section 13.2.4 of the
Lustre 1.8 Operations Manual.     What is the purpose of the

mdt1# tunefs.lustre --mgs --mdt --fsname=testfs /dev/sda1

command?    I assume it is writing this information to the MDT (/dev/
sda1) but wan't that information alright put there when the file
system was created under 1.6.4.2?    Has the format changed between
the two versions?    Why is the tunefs.lustre step necessary?    I'm
concerned about overwriting *anything* on the MDT and rendering our
file system unusable.   I just want to be sure we understand what we
are doing.

The paragraph labeled "Description" in section 32.2 (describing
tunefs.lustre) did not exactly give me a warm-fuzzy.

BTW, we already have a number of 1.8.0.1 clients running against the
1.6.4.2 servers.     Working great so far!

Thanks,

Charlie Taylor
UF HPC Center