Skip Navigation Links | |
Exit Print View | |
![]() |
Sun QFS and Sun Storage Archive Manager 5.3 Release Notes Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
2. Significant Bugs Fixed in This Release
samst Driver Fails to Attach While Adding the SUNWsamfsu and SUNWsamfsr Packages
sammkfs Command Does Not Support the -A Option if the SUNWqfs Package Is Installed
samst and sgen Drivers in SAM-QFS
Solaris I/O Multipathing and Direct-Attached StorageTek Libraries
This section describes some special notes about the Sun QFS and Sun Storage Archive Manager software.
If you are already running SAM-QFS versions 5.0 or later, you can upgrade to the next incremental release by performing a rolling upgrade without taking down the rest of the file system. At any given time, the metadata server and the clients can be only one release apart. To perform a rolling upgrade, your environment must include one primary metadata server and at least one potential metadata server.
Follow these steps:
Upgrade the potential metadata server.
Failover to the potential metadata server.
Upgrade the primary metadata server.
Failover to the primary metadata server.
Upgrade the clients.
With the advent of larger tape sizes being supported by SAM-QFS, the page size as reported by samu and the file system manager GUI may be confusing. The size reported by SAM-QFS has always been in “powers of two” units. For example, 1 Gbyte = 1,073,741,824 bytes and 1 Tbyte = 1,099,511,627,776 bytes. If you are using a 5–Tbyte T10000C tape which is 5,000,000,000,000 bytes, SAM-QFS will report it as 4.54 Tbytes.
For reference, the reported units can be changed to “powers of 10” units by doing the following math:
4.54 Tbytes * 1,099,511,627,776/1,000,000,000,000 = 5.0 Tbytes (where 1,099,511,627,776 is 1 Tbyte)
Similar calculations can be done to convert Gbytes into “power of 10” Gbytes.