Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide

This chapter describes the content of the release packages and shows the directories and files that the software creates when it is installed. Specifically, it contains the following topics:

• Release Package Contents
• Directories and Files Created

---

Release Package Contents

The Sun StorEdge QFS and the Sun StorEdge SAM-FS software packages are in Sun Solaris pkgadd(1M) format. These packages reflect the Sun Solaris version for the platform upon which you will be installing the Sun StorEdge QFS or the Sun StorEdge SAM-FS software.

For information on the directories and files provided with the release package, see the Sun StorEdge QFS and Sun StorEdge SAM-FS 4.1 Release Notes, which is posted to the documentation web sites described in this manual's preface.

TABLE 2-1 shows the release packages.

The releases are identified using characters arranged in the following format:

major.minor.patch

TABLE 2-2 explains the release numbering scheme.

Examples:

• 4.0 is a major release with no minor release revisions and no bug fixes.
• 4.1 is a minor release.
• 4.1.1 is a patch release that contains software fixes for a major or minor release. This number appears in the patch's README file.

---

Directories and Files Created

This section describes the directories and files associated with the Sun StorEdge QFS and Sun StorEdge SAM-FS products. You can obtain additional information about the files in this section from the man pages after the software is installed.

Directories Created at Installation

TABLE 2-3 lists the directories created when the Sun StorEdge QFS and Sun StorEdge SAM-FS software packages are installed.

Files Created at Installation

TABLE 2-4 and TABLE 2-5 list the files created when the Sun StorEdge QFS or Sun StorEdge SAM-FS software is installed.

The Sun StorEdge QFS and Sun StorEdge SAM-FS file systems have dynamically loadable components that are stored in the Sun Solaris /kernel directory (see TABLE 2-4). You can determine the modules that are loaded by using the modinfo(1M) command. Typically, the kernel loads the file system module at boot time. Alternatively, you can load the file system module when the file system is first mounted after the Sun software is installed.

After the Sun StorEdge QFS or Sun StorEdge SAM-FS software is installed, it creates files that it uses for fault notification. TABLE 2-5 lists these files. When the software detects faults serious enough to merit user attention, the software uses these trap and log files to convey fault information through the SAM-QFS Manager software.

The software creates the files listed in TABLE 2-5 with -rwxr-x--- permissions. Do not change these file permissions. If execute permissions are lost, for example, the system writes messages such as the following to /var/adm/messages:

SUNW,SUNWsamfs,sysevent.conf, line1: no execute access to /opt/SUNWsamfs/sbin/tapealert_trap - No such file or directory.

Site Files

The configuration procedures in this manual direct you to create several files. The Sun StorEdge QFS and Sun StorEdge SAM-FS software uses these site files.

TABLE 2-6 and TABLE 2-7 list the site files you create. Some of the files in these lists are optional, depending on your configuration, and others are required.

TABLE 2-6 shows the required site files. These are files that you must create at your site in order to use the Sun StorEdge QFS and Sun StorEdge SAM-FS software.

TABLE 2-7 shows the optional site files. This is a partial list of the files that you might or might not create depending on the software packages you install and the features you use.

Modified System Files

During installation, Sun StorEdge QFS and Sun StorEdge SAM-FS software adds information to certain Sun Solaris system files. These system files are ASCII text files. Sun Solaris uses these files to identify loadable kernel modules by number rather than by name.

The Sun StorEdge QFS and Sun StorEdge SAM-FS software adds information to the following files:

• /etc/name_to_sysnum. This is the system call information file, and it is used by both Sun StorEdge QFS and Sun StorEdge SAM-FS software. The samsys system call number can vary depending on the system call numbers in use by the Sun Solaris software. If no samsys entry exists, the system adds the following line:

samsys 182

Certain Solaris OS patches might either remove or introduce conflicts with the samsys entry. For information on installing Solaris OS patches in a Sun StorEdge QFS or Sun StorEdge SAM-FS environment, see Installing Sun Solaris Patches.

• /etc/name_to_major. This file maps drivers to major numbers. The Sun StorEdge SAM-FS software uses this file. The samst and samrd major numbers can vary depending on the major numbers in use by the Sun Solaris software. The system adds the lines shown in CODE EXAMPLE 2-1.

CODE EXAMPLE 2-1 Lines Added to /etc/name_to_major

samst 63 samrd 64

• /etc/security/auth_attr. This file is the authorization description database, and it is used by both Sun StorEdge QFS and Sun StorEdge SAM-FS software. The system adds the lines shown in CODE EXAMPLE 2-2.

CODE EXAMPLE 2-2 Lines Added to /etc/security/auth_attr

com.sun.netstorage.samqfs.web.read:::SAM-FS Read Access:: com.sun.netstorage.samqfs.web.write:::SAM-FS Write Access:: com.sun.netstorage.samqfs.web.*:::SAM-FS All Access::

• /etc/user_attr. This file is the extended user attributes database. The SAM-QFS Manager uses this file. The system adds the lines shown in CODE EXAMPLE 2-3.

CODE EXAMPLE 2-3 Lines Added to /etc/user_attr

SAMadmin::::type=role;auths=com.sun.netstorage.samqfs.web.* samadmin::::type=normal;roles=SAMadmin

Installing Sun Solaris Patches

Certain Sun Solaris patches overwrite the /etc/name_to_sysnum file. The /etc/name_to_sysnum file identifies loadable kernel modules by number rather than by name. If a patch overwrites the /etc/name_to_sysnum file, it removes the Sun StorEdge QFS and Sun StorEdge SAM-FS samsys system call number entry. Without a system call number, you can cause a system panic or a mount failure to occur when you attempt to mount Sun StorEdge QFS or Sun StorEdge SAM-FS file systems.

CODE EXAMPLE 2-4 shows the messages that the Solaris OS writes to the /var/adm/messages file.

WARNING: system call missing from bind file

WARNING: SAM-QFS: modload(samsys) failed.

WARNING: The file /etc/name_to_sysnum must contain a "samsys" entry.

WARNING: The SAM-QFS system call number must be unique in /etc/name_to_sysnum

WARNING: and not assigned in /usr/include/sys/syscall.h  (Note: entries named

WARNING: "SYS_reserved_#" are available). The suggested default SAM-QFS entry

WARNING: in /etc/name_to_sysnum is "samsys 182". If system call 182 cannot

WARNING: be used for SAM-QFS, use an alternate entry, such as "samsys 183".

WARNING: After changing /etc/name_to_sysnum a reboot is required.

To avoid this problem, use the following procedure for installing Solaris OS patches.

1. Idle archiving and stop the storage and archive manager. (Optional)

Perform this step only if you are using the Sun StorEdge SAM-FS file system. You do not have to perform this step if you are using the Sun StorEdge QFS file system. Type the following commands:

# samcmd aridle

# samd stop

2. Use the cp(1) command to save your current /etc/name_to_sysnum file to an alternate location.

For example:

# cp /etc/name_to_sysnum /etc/name_to_sysnum.old

3. Install one or more Solaris OS patches.

For information about this, consult the documentation that came with your Solaris OS patch.

4. Use vi(1) or another editor to open the /etc/name_to_sysnum file and search for lines containing the string samsys.

Depending on your search results, go to one of the following procedures:

• If your /etc/name_to_sysnum file does not contain any lines containing the samsys string, you need to add them. Go to To Add a samsys Entry to /etc/name_to_sysnum for information on doing this.
• If your /etc/name_to_sysnum file contains a samsys entry line, you need to verify that it is still a valid entry. Go to To Verify a samsys Entry in /etc/name_to_sysnum for information on doing this.

1. Use more(1) or another viewer to examine file /usr/include/sys/syscall.h and select an available system call number for the samsys entry.

Within file /usr/include/sys/syscall.h, entries containing the string SYS_reserved_# indicate available system call numbers. Sun Microsystems recommends that you use number 182 for Sun StorEdge QFS and Sun StorEdge SAM-FS operations.

2. Use vi(1) or another editor to open file /etc/name_to_sysnum. (Optional)

Do not perform this step if you already have this file open.

3. Verify that the system call number you chose in Step 1 is available in /etc/name_to_sysnum.

Search through this file for the number you chose.

If your installation is already using 182 for a different application, you need to find the next available system call number and use it for the Sun StorEdge QFS and Sun StorEdge SAM-FS software. Repeat Step 1, Step 2, and Step 3 as often as necessary until you determine that the system call number you selected for Sun StorEdge QFS and Sun StorEdge SAM-FS operations is unique.

The rest of this procedure is written assuming that 182 is an available system call number at your site. Modify the instructions in this procedure if you select another number.

4. Add the samsys line that is recommended for the 4.1 releases.

To add number 182, add the following line to /etc/name_to_sysnum:

samsys 182

5. Add the following samsys line if you plan to fall back to the 3.5.0 releases. (Optional)

If you want to be able to fall back to the Sun QFS and Sun SAM-FS 3.5.0 releases, add the following line:

samsys64 181

6. Save and close /etc/name_to_sysnum.

7. Reboot the system.

8. Delete the backup file when all is determined to be running correctly.

For example:

# rm /etc/name_to_sysnum.old

1. Use more(1) or another viewer to examine file /usr/include/sys/syscall.h and verify that the system call number for the samsys entry is still available.

Within file /usr/include/sys/syscall.h, entries containing the string SYS_reserved_# indicate available system call numbers. Sun Microsystems recommends that you use number 182 for Sun StorEdge QFS and Sun StorEdge SAM-FS operations.

2. Use vi(1) or another editor to open file /etc/name_to_sysnum. (Optional)

Do not perform this step if you already have this file open.

3. Verify that the system call number you chose in Step 1 is still available in /etc/name_to_sysnum.

Search through this file for the number you chose.

It is possible that your installation is already using 182 for a different application. If this is the case, you need to find the next available system call number and use it for the Sun StorEdge QFS and Sun StorEdge SAM-FS software.

The rest of this procedure is written assuming that 182 is an available system call number at your site. Modify the instructions in this procedure if you select another number.

4. Determine which samsys lines exist in your /etc/name_to_sysnum file and edit the file as necessary.

TABLE 2-8 shows the lines that could exist and prescribes the action to take.

5. Save and close /etc/name_to_sysnum.

6. Reboot the system.

7. Delete the backup file when all is determined to be running correctly.

For example:

# rm /etc/name_to_sysnum.old

Sun StorEdge QFS & Sun StorEdge SAM-FS Software Installation & Configuration Guide

817-4092-10

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.