This topic describes how to upgrade the SAN File System package
repository on a metadata server engine.
Prerequisites
You must be logged in with root privileges to upgrade the package
repository.
Context
The SAN File System package repository holds all the packages needed
to install the various SAN File System software components, including the
metadata server, the administrative server, and all clients. By default, these
packages are installed in /usr/tank/packages.
You need to perform this procedure
on each metadata server engine in the cluster.
Note: - A single up-to-date package repository can be used to serve packages to
the entire SAN File System. However, to avoid the accidental installation
of down-level packages and for high availability, keep all copies of the package
repository up to date.
- If the name of the updated package has not changed since the previous
version, the package is overwritten. To keep backup copies of old packages,
you should copy them from /usr/tank/packages to some other location.
Steps
- Insert the SAN File System CD-ROM into the CD-ROM drive, and then
mount CD-ROM drive.
mount /media/cdrom
- If you have all engines attached to a single KVM, switch the monitor
to this engine. Otherwise, establish an SSH session from the master console
to the engine.
- Determine the name of the currently installed package
repository.
rpm - qa | grep sfs-package
- Install the new package repository:1
/media/cdrom/install/install_sfs-package-2.2.0-104.i386.sh
- When prompted for your preferred language, type the number that
corresponds to your preferred language and press Enter.
- When prompted to view the International Program License Agreement
press Enter.
- After reading and agreeing to the license (by pressing Enter to
page forward and typing 99 and pressing Enter to page backwards),
type 1 and press Enter to accept the license agreement and install
the software.
Postrequisites
Continue with the next metadata server in the cluster until you have
upgraded the package repository on all metadata server engines.
1 If the new
package repository name is different than the existing package repository,
remove the existing package repository.
rpm -e existing_package_repository_name