Thanks Brian, but I'm still a little unsure of the tunefs step in the
upgrade. Is it actually necessary as part of the MDS upgrade? Is
it safe and do we do the same when upgrading the OSSs i.e. do we have
to run tunefs.lustre on each OST or just the MDT?
Thanks,
Charlie Taylor
UF HPC Center
On Jul 23, 2009, at 9:47 AM, Brian J. Murrell wrote:
Charles,
I have opened bug 20246 to have that section of the manual reviewed.
Thanx for pointing that out.
b.
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss
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
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss