
           Sun StorEdge QFS and Sun StorEdge SAM-FS 4.1 Release Notes
                       =============================
                                12 May 2004

The Sun StorEdge QFS and Sun StorEdge SAM-FS 4.1 releases incorporate
design and feature changes, function enhancements, and bugfixes over
previous releases.  System administrators and programmers familiar
with these software products will see changes that can affect daily
operations and can affect automated scripts written to co-exist with
this software.

For these reasons, Sun Microsystems, Inc. recommends that you study this
README file prior to upgrading to the Sun StorEdge QFS or Sun StorEdge
SAM-FS 4.1 releases.

             =======================================================
                                     NOTE

             This README file is an unchanging file.  It was created
             prior to the creation of the final software release
             packages.  For complete and up-to-date information
             pertaining to the 4.1 release, see the "Sun StorEdge
             QFS and Sun StorEdge SAM-FS Release Notes" available on
             the following websites:

             - docs.sun.com
             - www.sun.com/products-n-solutions/hardware/docs
               /Software/Storage_Software

             If you are installing a patch, see the patch README
             that is distributed with the software patches for
             additional information.

             If you are installing this product's base release
             and its software patches, Sun Microsystems recommends
             that you study the "Sun StorEdge QFS and Sun StorEdge
             SAM-FS Release Notes" *and* the patch README files
             distributed with the software patches.  The patch
             README files contain information that supplements the
             information in this README and in the release notes.

             =======================================================

             The information in this README file is superseded by
             the information in the release notes.
             This README file will not be distributed in future
             major releases of the Sun StorEdge QFS and Sun StorEdge
             SAM-FS software.

             =======================================================


Sun StorEdge SAM-FS 4.1 software is distributed through your reseller
or Authorized Service Provider.  The release software CD-ROM is
available upon request; a fee for processing media requests is
charged.  All required and optional packages are included on the
CD-ROM.  Optional, separately licensed products such as the Sun
StorEdge QFS software package are also included on the Sun StorEdge
SAM-FS CD-ROM.

Documentation Updates
=====================
 * The Sun StorEdge QFS and Sun StorEdge SAM-FS documentation is
   available on the web at the following URLs:

   - docs.sun.com
   - www.sun.com/products-n-solutions/hardware/docs/Software/Storage_Software

 * The publications that support the 4.1 release are as follows:

   - Sun SAM-Remote Administrator's Guide, part number 816-2094-11

   - Sun QFS, Sun SAM-FS, and Sun SAM-QFS Disaster Recovery Guide,
     part number 816-2540-10

   - Sun StorEdge QFS and Sun StorEdge SAM-FS File System
     Administration Guide, part number 817-4091-10

   - Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and
     Configuration Guide, part number 817-4092-10

   - Sun StorEdge SAM-FS Storage and Archive Management Guide,
     part number 817-4093-10

   - Sun StorEdge QFS and Sun StorEdge SAM-FS Release Notes,
     part number 817-4094-10

 * Hard copy manuals are available from the following website:

   www.iuniverse.com


Features
========
 * Add IBM 3592 tape support to the IBM 3494 robot.

 * Operating system support.

   Sun StorEdge SAM-FS 4.1 supports the following Sun Solaris operating
   system (OS) levels:

   - Solaris 8 update 5 (07/01)
   - Solaris 9 update 3 (04/03)

 * Packaging changes.

   The SUNWsamfs and SUNWqfs packages have been split into root and
   usr packages.  SUNWsamfs is replaced by SUNWsamfsr (root) and
   SUNWsamfsu (usr).  SUNWqfs is replaced by SUNWqfsr (root) and
   SUNWqfsu (usr).

   Note: You must install the root package before the usr package,
         or pkgadd reports an error.

   Packages are delivered in directory format rather than datastream
   format.  For information on installing the software, see the
   Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation
   and Configuration Guide.

 * New device support.

   This release added support for the following new devices:

   - Sony PetaSite/S-AIT library

   - StorageTek SL8500 library

   - Overland Data Inc. Neo Series tape libraries.

   - Sony Super AIT drive.  A new media type, sa, has been added for
     the Sony Super AIT drive.  It is qualified as a standalone
     manually loaded drive.

   - StorageTek T9840C drive. The media type is sg, which is the
     same as the media type of the other StorageTek 9840 drives.

   - StorageTek T9940B drive.

   - Hewlett-Packard Ultrium 2 (LTO-2) drive.

   - Sun/Quantum SDLT320 drive.

   - IBM Ultrium 2 (LTO-2).  This drive requires firmware 38D0 or greater.

   - IBM 3590H drive.

 * Script changes.

   This release changed several command names and example script install
   directories.  The following paragraphs describe the command name
   changes and example script install directory changes that have been made.

   BugId 4949445 renamed .sh commands for 4.1.  Specifically, it eliminated
   the use of the .sh suffix from within the /opt/SUNWsamfs/sbin
   directory.

   The following command names and man page names were changed:

   --- old command name ---             --- new command name ---
   /opt/SUNWsamfs/sbin/info.sh          /opt/SUNWsamfs/sbin/samexplorer
   /opt/SUNWsamfs/sbin/set_admin.sh     /opt/SUNWsamfs/sbin/set_admin
   /opt/SUNWsamfs/sbin/trace_rotate.sh  /opt/SUNWsamfs/sbin/trace_rotate

   --- old man page name ---            --- new man page name ---
   info.sh                              samexplorer
   set_admin.sh                         set_admin
   trace_rotate.sh                      trace_rotate

   The target install directory changed for some of the example scripts
   found in directory /opt/SUNWsamfs/examples.  These scripts are
   automatically copied from the old location to the new location at
   installation time.  It is your responsibility to update these scripts
   with any changes that might have been made to the default versions.
   The system displays a message at installation time if they need to be
   updated.

   You might want to add /etc/opt/SUNWsamfs/scripts to your PATH
   environment if you run the following scripts directly.  However,
   this is unlikely.

   The default versions of the following required site-customizable
   scripts are automatically installed when the package or patch is
   installed:

   --- source directory ---             --- install directory ---
   /opt/SUNWsamfs/examples/archiver.sh  /etc/opt/SUNWsamfs/scripts/archiver.sh
   /opt/SUNWsamfs/examples/recycler.sh  /etc/opt/SUNWsamfs/scripts/recycler.sh
   /opt/SUNWsamfs/examples/save_core.sh /etc/opt/SUNWsamfs/scripts/save_core.sh
   /opt/SUNWsamfs/examples/ssi.sh       /etc/opt/SUNWsamfs/scripts/ssi.sh

   You can copy the default versions of the following optional
   site-customizable scripts after the package or patch is installed:

   --- source directory ---            --- install directory ---
/opt/SUNWsamfs/examples/dev_down.sh    /etc/opt/SUNWsamfs/scripts/dev_down.sh
/opt/SUNWsamfs/examples/load_notify.sh /etc/opt/SUNWsamfs/scripts/load_notify.sh
/opt/SUNWsamfs/examples/log_rotate.sh  /etc/opt/SUNWsamfs/scripts/log_rotate.sh

 * Added TapeAlerts.

   TapeAlert support was added for direct-attached libraries and tape drives.
   For more information, see tapealert(1M).

 * ACSLS support enhancements.

   This release added support for ACSLS 6.1, 6.1.1 and the Solaris version
   of ACSLS 7.0 and 7.1.

   This release supports one-step export of media from ACSLS-attached
   libraries.  See the export(1M) man page.  The CAP (Cartridge Access
   Port) must be in manual mode to support this feature.

 * Large device support (Extensible Firmware Interface (EFI) Labels).

   BugId 4729295 added support in Sun StorEdge SAM-FS and Sun StorEdge
   QFS 4.1 software for SCSI devices and Solaris Volume Manager volumes
   larger than 1 TB.  The file system must be built using 4.1; it is not
   possible to grow an existing file system onto large devices.

 * Continuous archiving.

   BugId 4700863 added continuous archiving Phase II.  Continuous
   archiving was accomplished by replacing the sam-arfind file system
   scanning mechanism with a file system change detection mechanism.  Each
   file system has a sam-arfind daemon executing a system call and
   requesting work.  As files are created or modified, the file system
   notifies sam-arfind.  sam-arfind determines the archive requirements
   for the file as defined in the archiver command file (archiver.cmd(4)).
   If the file is to be archived, the directory containing the file and
   the time for the archive action is recorded in an "ScanList" to be
   acted upon later.  The earliest time for archive action is also kept.
   When this time is reached, the ScanList is sorted by time, and the
   directories containing files to be archived are scanned, and the
   files scheduled for archival.  The ScanList is a file that is mapped
   and kept in the archiver data directory for the file system.  The
   ScanList is listed in the showqueue output.

   Continuous archiving yields noticeable performance improvements for
   file systems containing large numbers of files - greater than
   1,000,000.  These file systems require long times to scan, sometimes
   several days!  In most situations that involved large numbers of
   files, most of the files never needed archive activity - the files
   were archived in the past, and never changes.  Continuous archiving
   avoids scanning directories and the .inodes file, so these large
   file systems pose no burden on the archiver.

   In the event of a system crash or an unexpected stoppage of
   sam-arfind, a full directory scan is initiated as a background
   activity.

   The samu 'arrestart' command causes all archiver work in progress to
   be discarded and a full file system scan to be performed.

   If you do not want to use continuous archiving, specify the
   examine = scan directive in the archiver command file (archiver.cmd(4)).

 * Controlling examination of a file system by the archiver

   BugId 4740478 provided file system scanning alternatives.  You
   can use the 'examine=method' directive in the archiver.cmd file to
   specify the file system examination mode, as follows:
   .  If the examine method is 'scan', a traditional scan is used.  The
      first scan is a directory scan, and all successive scans are inode
      scans.
   .  If the examine method is 'scandirs', all scans are directory scans.
   .  If the examine value is 'scaninodes', all scans are inode scans.
   .  If the scan method is 'noscan', directories are scanned when the
      content changes and archiving is required.

   If the examine method is 'scandirs' and the archiver finds a directory
   with the archive(1) -n  (noarchive) attribute set, that directory
   is not scanned.  The noarchive attribute allows the system
   adminstrator to identify directories and subdirectories that contain
   files for which no more archiving is needed.  These could be read-only
   files that have already been archived, for example.  Using the
   noarchive attribute to identify files and subdirectories for which all
   archive copies have been made can dramatically reduce the work
   required to examine a file system.

   The samu(1M) 'arscan fsname[.directory | ..inodes] [delay]' command
   causes the archiver to scan a file system.  With no options, the file
   system is scanned recursively from the root.  The '.inodes' option
   causes an inodes scan.  The 'directory' option causes the named
   directory to be scanned.  The optional 'delay' (seconds) may be used
   to delay the scan.

 * Initiating the archiving of files.

   As files are identified to be archived, they are placed in a list known
   as an Archive Request.  The Archive Request is scheduled for archival
   at the end of a file system scan.  The following archive set parameters
   have been added to better control the archiving workload, and assure
   timely archival of files:

   '-startage' sets the interval between the first file to be archived in
   the Archive Request and the start of archiving.  This allows time to
   accumulate archival work after the first file has been scheduled for
   archival.

   '-startcount' sets the start archiving file count.  When 'startcount'
   files have been identified for archival in the Archive Request, the
   archival operation will begin.

   '-startsize' sets the minimum total size of all files to be archived in
   the Archive Request.  This allows the accumulation of archival work to
   be based on the total size of the files that have been scheduled for
   archival.

   If more than one of '-startage' and '-startcount' and '-startsize
   are set, the first condition encountered initiates the archival
   operation.  If none are set, the archival operation starts at the
   end of a file system scan.

   For more information, see archiver.cmd(4).

 * Archiver "notify" script changes.

   The archiver notify script "archiver.sh" has been moved from
   /opt/SUNWsamfs/sbin to /etc/opt/SUNWsamfs/scripts.  This is the
   location of the default archiver notify script.

   The archiver now maintains its own record of the messages pertaining to
   issues preventing archiving such as "no space" and "no volumes".  The
   directories '/var/opt/SUNWsamfs/archiver/NoSpace' and
   '/var/opt/SUNWsamfs/archiver/NoVsns' are no longer used.

 * Archiver command file reading.

   BugId 4756625 removed the automatic reread of a changed archiver.cmd
   file.  Previously, the archiver command file was reread sometime in
   the next 60 seconds after it was changed.  When reconfiguring Sun
   StorEdge SAM-FS software, it is often necessary to change the
   archiver command file.  At some time in the process, the configuration
   files are out of sync.  If you change the archiver.cmd file before
   the others, the archiver automatically rereads the changed file, and
   finds errors in it.

   Now, the archiver only rereads the archiver command file when it
   receives a SIGHUP.  This occurs automatically when sam-fsd receives
   a SIGHUP.

 * Archiver extensions to 'allsets'.

   The 'allsets' feature for defining Archive Set parameters is extended
   to allow the use of a copy number.  That is, 'allsets.copy'.  This
   allows parameters to be defined for only a single Archive Set Copy.
   Previously, any parameters assigned by 'allsets' applied to all
   Archive Set Copies.

   The 'allsets' and 'allsets.copy' parameters can be used to define volume
   assignments.  VSNs defined for 'allsets' and 'allsets.copy' are applied
   to any Archive Sets that do not have a VSN definition.

   For more information, see the archiver.cmd(4) man page.

 * Archiving metadata.

   BugId 4765714 changed metadata archiving.  For Version 1 file systems,
   the archiver archived directories, removable media files, segment
   index inodes, and symbolic links as metadata.  In Version 2 file
   systems, the removable media files and symbolic links are stored in
   inodes rather than data blocks.  In 4.0, they were not archived.

   Now, only directories are archived as metadata.  Symbolic links are
   archived as files in user-defined Archive Sets.  This change
   provides consistent behavior with the tar(1) command.

   For Version 1 file systems, the previous metadata archiving is
   preserved.

   BugId 4875268 provided a mechanism to suppress metadata archiving.
   Metadata archiving can be controlled by using the
   'archivemeta = [ on | off]' directive.

   For more information, see the archiver.cmd(4) man page.

 * Archiver soft restart.

   BugId 4758016 added a soft restart command for the archiver.
   When the archiver is stopped, for any reason (SIGINT, SIGTERM, SIGKILL
   etc.), and subsequently started by sam-fsd, any work that was in
   progress is recovered.

   The samu(1M) 'arrestart' command causes the archiver to discard all work
   in progress and restart all archiver daemons.

   A new samu(1M) 'arrerun' command causes the archiver to perform a soft
   restart.  The archiver daemons are restarted, and all work in progress
   is recovered.

 * Provision for choosing the time reference for unarchiving file copies.

   BugId 4811733 gave the user the choice of unarchiving by modify date
   instead of by access date.  The new '-unarchage time_ref' archive set
   parameter was added to allow the site to select which file time
   (access or modify) to use to determine when to unarchive a file copy.

   For more information, see the archiver.cmd(4) man page.

*  Separate scheduling for new versus rearchive operations.

   BugId 4788283 separated archival of new and recycled copies.  If an
   archive copy of a file is being rearchived, an internal Archive Set
   Copy is used for scheduling the archive operation.  It is called a
   Rearchive Set Copy, and it uses the archive parameters from the
   actual Archive Set Copy.  If desired, the Archive Set parameters
   and VSN associations can be set by using the Archive Set Copy name
   followed by the character 'R'.  The Rearchive Set Copy allows the
   users to differentiate 'new' and rearchive operations.  It also allows
   them to use different parameters and VSNs for each operation.

   For more information, see the archiver.cmd(4) man page.

*  Limiting archiver drive work.

   BugId 4826641 enabled the archiver to balance multiple drive usage.
   In 3.5.0, it was possible to limit the amount of work that a drive
   can do.  The analyst set the number of drives to use for an archive
   set to several times the number of physical drives.  This had the
   effect of dividing the load into smaller chunks.

   In 4.0, the archiver strictly scheduled only the drives available.  To
   get the effect of the 3.5.0 feature, the '-drivemax' archive set
   parameter was provided to to limit the amount of data that each arcopy
   writes.  This allows you to balance the drive work.

   For example, assume that there are 300G of data to archive in the
   ArchReq.  Using the parameters "-drives 5 -drivemax 10G" causes 5
   drives to be used and 10G of file data to be archived at a time on
   each drive.  This is equivalent to using "-drives 30" in 3.5.0.

   For more information, see the archiver.cmd(4) man page.

 * Limiting messages for archiving problems.

   BugId 4882171 kept ArchReqs for files that cannot be archived imminently.
   The archiver keeps ArchReqs for files that have persistent archiving
   problems in a "wait" queue.  The wait queue is also used for ArchReqs
   that are awaiting restart of idled or stopped archiving.

   The archiver maintains a record of which messages for the ArchReq have
   been sent to the sam log and to the archiver notify script.  Such
   messages are sent only once for each unschedulable ArchReq.

   Messages written to the ArchReq show the waiting condition.  You can
   use the showqueue(1M) command to view them.  You can also view
   the wait conditions in sam-archiverd display in samu(1M).

   The "wait" queue is examined and ArchReqs are rescheduled in the following
   situations:
     . sam-archiverd receives an 'arrun'.
     . A file system is mounted or unmounted.
     . Each time 'interval' has elapsed.
     . sam-archiverd receives SIGHUP or SIGALRM.
     . sam-archiverd receives a "CatalogChange" message.

 * Sorting files to be archived.

   BugId 4826460 gave the archiver the ability to sort files in reverse
   order.  The Archive Set parameter '-rsort' performs a sort in the
   reverse order of the '-sort' parameter.

 * Added a new command to remove archiver queue files (ArchReqs).

   BugId 4765449 added a command to remove an archive request.  The
   samu(1M) 'arrmarchreq fsname.[* | arname]' command allows the operator
   to remove one or more ArchReqs.  The command can take the following
   forms:
   samu(1M) Command:              Archive Request Removed:
   arrmarchreq fsname.*           All ArchReqs for file system 'fsname'
   arrmarchreq fsname.arname      The ArchReq 'arname'  e.g.'samfs1.1.145'
   arrmarchreq fsname.asname.n.*  All ArchReqs for Archive Set 'asname.n'

 * Provision to use file access time as Archive Set specifier.

   BugId 4948487 enabled the archiver to use file access time as the
   archive set specifier.  The '-access' specifier can be used on the
   archive set directive to include files whose access time is older
   than 'age'.  This allows files that have not been accessed for a
   long time to be rearchived to cheaper media.

 * Changes to the samu(1M) displays.

   Bugid 4721111 reorganized the samu(1M) help display to make the
   command and media help screens smaller.  There are now 9 help screens
   instead of 5.

   Bugid 4950099 enables the kernel statistics accumulated by Sun
   StorEdge SAM-FS to be displayed in the samu(1M) K display.

 * New samu(1M) commands.

   Bugid 4934616 adds additional mount point option commands to samu(1M).
   There are now 12 samu(1M) help screens.  The stager commands have been
   put in a separate help screen.  The new commands are as follows:
     forcedirectio, noforcedirectio
     sw_raid, nosw_raid
     hwm_archive, nohwm_archive
     mh_write, nomh_write
     suid, nosuid
     qwrite, noqwrite
     sync_meta eq value
     stripe eq value
     mm_stripe eq value
     wr_throttle eq value
     invalid eq value
     minalloc eq value
     maxalloc eq value
     aplease eq interval
     rdlease eq interval
     wrlease eq interval
     maxpartial eq value
     partial_stage eq value
     flush_behind eq value
     stage_flush_behind eq value
     stage_n_window eq value
     stage_retries eq value
     dio_rd_consec eq value
     dio_rd_form_min eq value
     dio_rd_ill_min eq value
     dio_wr_consec eq value
     dio_wr_form_min eq value
     dio_wr_ill_min eq value

   Bugid 4930356 added an additional 'priority' command to samu(1M).  This
   command sets the load priority for a volume in the preview queue
   (priority pid newpri).

 * Support for devices up to 16 TB.

   Bugid 4729295 enables disk devices up to 16 TB to be configured in
   Sun StorEdge QFS and Sun StorEdge SAM-QFS file systems.  File systems
   created on these large devices cannot be used with earlier versions
   of Sun StorEdge QFS or Sun StorEdge SAM-FS software, nor can it be
   used on Solaris operating system platforms prior to Solaris 9 4/03
   (update 3).  Large device support is only available when running a
   64-bit kernel.

 * chmed(1M) command option -i removed.

   Bugid 4963003 removed the ability to use the chmed(1M) -i command to
   set or clear the catalog "slot in use" (i) flag.  This option has not
   been useful since a catalog redesign in release 3.5.0, and it is
   being removed.

 * New samfsdump(1M) options.

   Bugid 4729238 added the -U option for dumping data for online files,
   as well as metadata for all files.  Note that this can make the dump
   file very large.  Take care to manage the increased size of the dump.

   Bugid 4965075 added the -P option to dump partial data for offline
   files that have the partial release option set.  Note that this can
   make the dump file very large.  Take care to manage the increased
   size of the dump.

 * New samfsrestore option.

   Bugid 4833549 added the -r option to replace existing files for cases
   in which the existing files have an older modification time than the
   dumped files.  If the existing files are newer they are not restored.

 * New releaser.cmd directive.

   Bugid 4767708 added the "list_size" releaser.cmd(4) directive.  This
   allows you to increase the number of releaser candidates above the
   default number of 10000 for file systems containing small files.
   For more information, see releaser.cmd(4).

 * New sfind(1) option.

   Bugid 4727090 adds the "partial_on" test as an sfind(1) option.  This
   test is true if the file has the partial release attribute set and
   the partially retained portion of the file is online.

 * Renamed the sam-ftpd daemon.

   Bugid 4768141 renamed the sam-ftpd daemon to sam-rftd (remote file
   transfer daemon).  The configuration file is now
   /etc/opt/SUNWsamfs/rft.cmd.  The /etc/opt/SUNWsamfs/ftp.cmd file is
   copied to /etc/opt/SUNWsamfs/rft.cmd automatically when upgrading
   from a 4.0 system.  When upgrading to 4.1, you must also change
   your daemon tracing commands in /etc/opt/SUNWsamfs/defaults.conf
   from "sam-ftpd" to "sam-rftd".

 * Single Port Multiplexing (SPM).

   Bugid 4768528 added infrastructure to Sun StorEdge QFS and Sun
   StorEdge SAM-FS software so that each uses only one listener port
   on a host for all product daemons.  This is instead of the daemons
   using one port per daemon. The list of daemons using SPM is:

   sam-rftd
   sam-amld

   The samu(1M) P display shows which services are available for connection.

   The samsock entries required in /etc/services for the 4.0 release
   are no longer needed for the 4.1 release.  If you do not anticipate
   falling back to the 4.0 release, you can remove the entries.

 * Stager daemon's log file enhancements.

   Bugid 4793471 standardized the date/time stamps of daemon log files
   and added the year to timestamp in the stager daemon's log file.
   The new format is yyyy/mm/dd hh:mm:ss.  This change also added the
   staged file's copy number, user id, group id, requestor's user id,
   and equipment ordinal of the drive upon which the file was staged
   to the log file.

   Bugid 4793476 added a 'start' event record in the stager daemon's
   log file.  A customer can currently request that the stage daemon
   collect staging event information and write a log file.  This
   feature allows a 'start' event to be recorded in the log file.  In
   the stager.cmd file, the customer can specify the following
   directive to specify the staging activities that are to be logged:

   logfile = filename [event]

   For event, specify start, finish, cancel, error, or all.  The default
   is finish, cancel, and error.

   These events are logged in the first column of the log entry as 'S'
   (start), 'F' (finish), 'C' (cancel), or 'E' (error).  This change
   also adds the equipment ordinal of the drive upon which the file was
   staged to the log file.

 * Disk archiving enhancements.

   Bugid 4756575 added the capability for disk archiving to write
   multiple files in tar(1) format to a single disk archive file.

   Bugid 4861558 addressed disk archiving performance problems
   attributed to transferring very large files across a wide area
   network by adding to configuration parameters.  The tcpwindow
   parameter can be used to set the socket buffer size.  The blksize
   parameter can be used to set the amount of data sent down the socket
   at a time.  The default block size is 1MB.  Both parameters can be
   set in the rft.cmd directives file.

   Bugid 4931705 appended the archive tar(1) file path to the disk
   volume name in the archiver log for disk archiving entries.

 * Total quotas.

   Bugid 4768337 added the capability to keep and enforce both total
   and online block quotas for Sun StorEdge SAM-FS file systems.

   Because metadata is not released, the values for files online and
   total limits are the same.  The new defaults for the quota and
   samquota(1M) commands show the total values and limits as well as
   the online values and limits.  For sparse files, the total block
   count reflects the number of blocks used if the file is online;
   the total block count reflects the actual size of the file if the
   file is offline.

 * Quota mount option defaults to 'on'.

   BugID 4965268 changed the quota mount option.  It now to defaults
   to quotas "on" if .quota_[agu] files are present.  If the quota
   files are present, then by default, the file system is mounted
   with quotas enabled.  If the quota files are missing, then no
   change in behavior should be apparent.  If quota files are present
   but you want to operate with quotas disabled, then you can specify
   the 'noquota' mount option.  (Allocating or freeing blocks or files
   when mounted with 'noquota' causes the quota files to become stale,
   so this is not recommended.)

 * SAM-Remote daemon trace files.

   Bugid 4900489 implemented daemon trace files for sam-serverd and
   sam-clientd.  You can control the daemon trace files by placing
   directives in the trace file section of defaults.conf configuration
   file.  The samset debug flag, 'remote', has been removed.

 * Catalog field to display volume information.

   Bugid 4898485 added a new field to the catalog that displays
   information on each volume.  This field can contain up to 128
   characters, and you can modify it by using the chmed(1M) command.
   You can use this field to display information such as the location
   of exported media or archive sets on a volume.

 * Mount option to override NFS sync.

   Bugid 4944054 added a new mount option, force_nfs_async.  The
   force_nfs_async option causes the file system to cache NFS data
   written to the server even if NFS has requested that the data be
   written synchronously through to disk.  samu(1M) includes the
   force_nfs_async and noforce_nfs_async commands, and samu(1M)
   includes the corresponding flags in the samu(1M) N display.

   For more information, see the mount_samfs(1M) man page.

* Mount option to refresh at eof for multireader.

  Bugid 4983767 added a new mount option, refresh_at_eof.  The
  refresh_at_eof mount option causes the current file size to be
  refreshed when the read buffer exceeds the end of file.  The
  refresh_at_eof and norefresh_at_eof commands are added to samu(1M)
  and the corresponding flags are displayed in the samu(1M) N display.

  For more information, see the mount_samfs.1m man page.

* Mount option to disable archiving, staging, and releasing.

  Bugid 4944364 added a new mount option, nosam, that mounts the Sun
  StorEdge SAM-FS product with only the file system functionality
  enabled.  ENOSPC is returned when the file system reaches 100% capacity.

* Mount option to disable file system scans.

  Bugid 4944357 added a new mount option, noscan, that disables the file
  system scans typically performed by the sam-arfind daemon.  These scans
  are responsible for finding archive candidates on the mounted file system.
  This mount option can be useful for file systems in which new files are
  no longer being created, yet staging and releasing are still desired.

* Changes to archive_audit exit codes.

  BugId 4887944 added new exit codes to archive_audit(1M).

  In cases for which the software returned success for non-fatal errors,
  it now returnes a nonzero result code.  User scripts that use
  archive_audit(1M) might need to be modified.

  For more information on error codes, see the archive_audit(1M) man page.

* License file location change.

  Bugid 4934418 changed the location and name of the license file to
  /etc/opt/SUNWsamfs/LICENSE.4.1.  Licenses generated for Sun StorEdge
  SAM-FS or Sun StorEdge QFS 4.0 software work with 4.1.

  NOTE: If you made changes to your site's configuration during the
  upgrade procedure, you might need a new license in order for the
  configuration changes to work correctly.

* SNMP traps support for Sun StorEdge SAM-FS software.

  Bugid 4768083 enabled you to configure the Sun StorEdge QFS and Sun
  StorEdge SAM-FS software to notify you when potential problems occur
  in its environment via SNMP traps.

  You can monitor a Sun StorEdge SAM-FS system remotely from a network
  management console.  Supported management consoles include the following:

  - The Storage Automated Diagnostic Environment (StorADE)
  - The Sun Management Center (Sun MC)
  - The Sun Remote Server (SRS)
  - The Sun Remote Server NetConnect

  Active fault determination and enhanced diagnostic support of Sun
  StorEdge SAM-FS systems is achieved with an asynchronous notification.
  You can enable and disable this feature through the 'alerts=on|off'
  directive in the defaults.conf(4) file.

* Pre-4.1 GUI tools removed.

  The libmgr(1M), samtool(1M), robottool(1M), devicetool(1M), and
  previewtool(1M) graphical user interfaces have been removed.  The
  SAM-QFS Manager replaces the functionality formerly found in these
  tools.
  

* SAM-QFS Manager 1.0 release.

  The SAM-QFS Manager 1.0 is a web-based graphical user interface tool
  for configuring and monitoring a Sun StorEdge QFS or Sun StorEdge
  SAM-FS environment.  The software consists of two components:

  - The Sun StorEdge QFS or Sun StorEdge SAM-FS server software is the
    first component.  It is installed when you install the SUNWsamfsr
    & SUNWsamfsu packages or the SUNWqfsr & SUNWqfsu packages.

  - The SAM-QFS Manager 1.0 application is the second component.  It
    consists of the SUNWsamqfsuir and SUNWsamqfsuiu packages.  You
    must install this component on the management station.

  SAM-QFS Manager Installation
  ----------------------------
  The Sun StorEdge QFS and Sun StorEdge SAM-FS Installation and
  Configuration Guide includes instructions for installing the SAM-QFS
  manager.  You can install and configure SAM-QFS Manager along with
  the file systems, or you can install it later.  If you install it
  later, use the instructions in the installation guide.

  The SAM-QFS Manager software package has hardware and software
  requirements beyond that of Sun StorEdge QFS and Sun StorEdge SAM-FS
  software.  Please refer to the Sun StorEdge QFS and Sun StorEdge SAM-FS
  Installation and Configuration Guide for more information on these
  requirements.

  Security
  --------
  For security reasons, the management console ends your https
  session after 15 minutes.  You have to log in again to resume.

  You must secure the management station and the Sun StorEdge SAM-FS
  and Sun StorEdge QFS servers that are managed.  Place it inside
  the firewall.

  Using the SAM-QFS Manager in Existing Sun StorEdge QFS or
  Sun StorEdge SAM-FS Environments
  --------------------------------
  If you install the SAM-QFS Manager in an environment that already
  includes Sun StorEdge QFS or Sun StorEdge SAM-FS file systems,
  the software reads the existing configuration information and
  presents this information to you for modification and/or
  viewing.

  Propagating Configuration File Changes
  --------------------------------------
  If you change any configuration files manually, you are
  responsible for the correctness of the files you change.
  Such configuration files include /etc/opt/SUNWsamfs/mcf,
  /etc/opt/SUNWsamfs/archiver.cmd, etc.  You can use the
  /opt/SUNWsamfs/sbin/archiver -lv command to check the correctness
  of the archiver.cmd file.

  Limitations
  -----------
  The SAM-QFS Manager 1.0 does not interoperate with all Sun StorEdge
  QFS and Sun StorEdge SAM-FS features, but depending on your equipment,
  configuration, and environment, it can simplify Sun StorEdge
  SAM-FS and Sun StorEdge QFS software configuration and control.
  Specifically, the SAM-QFS Manager does not support the following
  features:

  - Sun Cluster software.

  - Sun SAM-Remote software.

  - Optical media.

  - EFI disk labels.

  - Fibre Channel bridge cards.  You cannot use the SAM-QFS Manager
    to configure an L25 or L100 tape library that contains a
    Fiber Channel bridge card (SCSI-to-FC bridge, SG-XFC420CARD-MOD).

  - Sun StorEdge QFS Shared File System.  You cannot configure a Sun
    StorEdge QFS shared file system, but the SAM-QFS Manager displays
    information for existing Sun StorEdge QFS shared file systems.
    Depending on how you have your environment configured, you might
    have to configure a new server in the SAM-QFS Manager if you
    failover a Sun StorEdge QFS shared file system.

  The Sun StorEdge QFS and Sun StorEdge SAM-FS software includes
  a complete command line interface that allows you to configure and
  monitor the features that the SAM-QFS Manager does not support.

  Single-user Administration
  --------------------------
  Any Sun StorEdge SAM-FS or Sun StorEdge QFS server can be
  administered by a single instance of the Sun Web Console.  Any
  server can be administered by a single username with SAMadmin
  privileges at any given point in time.

  The SAM-QFS Manager 1.0 release does not support multiple instances
  of the SAMadmin role managing the same server or multiple instances
  of Sun Web Console managing the same server.  It is important to
  note that this includes opening another browser window and
  manipulating the Sun StorEdge QFS and Sun StorEdge SAM-FS
  configuration.  It is the responsibility of the site
  administrator(s) to comply with this policy.

  The administrator should log on as "samadmin" and choose "SAMadmin"
  on the Role selection page.  All other users should log on as
  "samuser".  If you want to create additional admin or user roles,
  please read the Sun StorEdge QFS and Sun StorEdge SAM-FS
  Installation and Configuration Guide.

* Sun Cluster 3.1 4/04 Interoperability with Sun StorEdge QFS software
  
  Sun Cluster 3.1 4/04 supports failover of standalone (non-shared)
  Sun StorEdge QFS file systems via the HAStoragePlus resource
  type implementation with the Sun StorEdge QFS 4.1 release.

  The ability to configure Sun StorEdge QFS software as a highly available
  local file system is supported on Solaris 9 OS platforms only.  This
  capability is not supported on Solaris 8 OS platforms.

  /etc/vfstab requirements
  --------------------------

  To configure Sun StorEdge QFS for failover with HAStoragePlus, configure
  the /etc/vfstab files on all applicable cluster nodes in the usual
  way with the following information:

  o The block special file in /etc/vfstab must be the Sun StorEdge
    QFS Family Set name.

  o The vfstype field must contain "samfs".

  o The mount-at-boot field must be set to "no".

  o The vfstab entry must be identical on all cluster nodes that can
    mount the file system.

  Specify the entry "sync_meta=1" in either /etc/vfstab or
  /etc/opt/SUNWsamfs/samfs.cmd.

  Example.  The following is a sample /etc/vfstab entry:

     qfs1 - /local/qfs1 samfs 3 no sync_meta=1

  In this example:

  o qfs1 is the Sun StorEdge QFS Family Set name.
  o /local/qfs1 is the mount point.  Must exist on all nodes.
  o samfs is the type of the file system.
  o The mount-at-boot field is set to "no".
  o The sync_meta=1 option is used here as recommended in
    order for metadata operations to survive a failover.

  /etc/opt/SUNWsamfs/mcf requirements
  -----------------------------------

  The Sun StorEdge QFS Family Set name specified in /etc/vfstab
  must be a valid Sun StorEdge QFS Family Set that is present
  in the mcf file.

  The mcf file entry can contain following types of Sun Cluster
  device names:

  o /dev/md/*: A SVM device pathname.

  o /dev/vx/*: A VxVM device pathname. Note that Veritas devices
               must be registered with the SunCluster framework
               using scsetup(1M) before they can be used.

  o /dev/global/*: Raw global devices.

  Please note that use of did devices of the form /dev/did/* is
  *not* supported.

  Example.  The following is an example mcf file entry for use with
  HAStoragePlus using raw devices:

     qfs1                   1   ma    qfs1     on
     /dev/global/dsk/d4s0  11   mm    qfs1     
     /dev/global/dsk/d5s0  12   mr    qfs1     
     /dev/global/dsk/d6s0  13   mr    qfs1     
     /dev/global/dsk/d7s0  14   mr    qfs1     

  Example.  The following is an example mcf file entry for use with
  HAStoragePlus using SVM metadevices. The example assumes
  that the SVM metaset in use is named "red".

     qfs1                   1   ma    qfs1     on
     /dev/md/red/dsk/d0s0  11   mm    qfs1     
     /dev/md/red/dsk/d1s0  12   mr    qfs1     

  Example.  The following is an example mcf file entry for use with
  HAStoragePlus using VxVm devices. 

     qfs1                    1   ma    qfs1     on
     /dev/vx/rdsk/oradg/m1  11   mm    qfs1     
     /dev/vx/rdsk/oradg/m2  12   mr    qfs1     

  The mcf file entry must be identical on all cluster nodes that
  are possible masters of the sun StorEdge QFS file system.

  Configuring the HAStoragePlus resource
  --------------------------------------

  While using HAStoragePlus to configure a Sun StorEdge QFS file system
  for failover, the FilesystemCheckCommand property of HAStoragePlus
  must be set to /bin/true.  All other resource properties for
  HAStoragePlus apply as specified in SUNW.HAStoragePlus(5).

  Example.  The following is an example command line that uses the
  scrgadm(1M) command to configure a HAStoragePlus resource.

     # scrgadm -a -g qfs-rg -j ha-qfs -t SUNW.HAStoragePlus \
        -x FilesystemMountPoints=/local/qfs1 \
        -x FilesystemCheckCommand=/bin/true

  Notes
  -----

  1. Sun StorEdge SAM-FS software is not supported.  That is, use
     of storage and archive management software (SAM) configurations
     with Sun StorEdge QFS is not supported.

  2. Using a Sun StorEdge QFS file system as the underlying native
     file system for use with cluster file system is not supported.

  3. Any failover application that is supported with Sun Cluster
     software is supported with Sun StorEdge QFS software as a 
     highly available local file system.  Support is not limited
     to specific applications.

Known Issues
============

* SAM-QFS Manager issues.

  - If you are using Internet Explorer 6.0, click the login button
    to log in.  A known problem exists regarding pressing the Enter
    key after typing the password when logging in.

  - While adding a Sun StorEdge SAM-FS or Sun StorEdge QFS host by
    using the Add button from the Sun StorEdge SAM-FS or Sun StorEdge
    QFS Servers page, use either the hostname or the IP address.
    Do not add the same host using both the hostname and the IP address.

  - Do not close the pop-up window by clicking the "X" button on the
    left top corner of the wizard screen in Internet Explorer or by
    clicking the "-" button in Netscape or Mozilla.  Always click on
    the "Cancel" button to exit.  If the wizard button is disabled,
    click on the other Tab in the application and click on the Tab
    for the action you want to perform.  The wizard button should
    then be enabled.  The wizards include:

    + Add Filesystem Wizard
    + Grow Filesystem Wizard
    + New Archive Policy Wizard
    + Apply Archive Policy to Filesystem Wizard
    + Add Tape Library Wizard
    + Add Stand Alone Tape Drive Wizard
    + VSN Reservation Wizard

  - In a wizard, the user input values are lost if the user navigates
    between the STEPS tab and the HELP tab inside a wizard.  Likewise,
    input values are also lost if the user navigates between STEP LINK
    on the left hand side on the wizard.

  - Each archiving file system on a Sun StorEdge SAM-FS or Sun SAM-QFS
    server has a default archive copy that archives all files that are
    not explicitly members of an archive policy.  If an archiver.cmd(4)
    file exists on the server, there must be a VSN association for each
    file system's default archive copy.

    When you create a file system through the web browser, and an
    archiver.cmd(4) file already exists, the SAM-QFS Manager software
    automatically creates a VSN association to an available or valid
    media type for the default archive copy.

    If an archiver.cmd(4) file does not exist on the server when you
    create a file system, the VSN association is not explicitly created
    and the default archiving behavior is retained.  In this situation,
    you can then create an archive policy from the Archive Management
    tab and apply the policy to the file system.  This action creates
    the archiver.cmd file and creates the necessary VSN association for
    the file system's default archive copy.

    To change these default copy definitions, you can manually edit the
    archiver.cmd(4) at a later time.

  - The following messages sometimes appear when a user tries to
    bring up the SAM-QFS Manager in a browser:

    + "Connect to <hostname.domain>:6789 failed (connection refused)"

    + "The connection was refused when attempting to contact 
       <hostname.domain>:6789"

    The system generates these messages under the following conditions

       1. The user typed in wrong URL (wrong hostname, domain, port etc.)

       2. The webserver is not running at the hostname specified

       3. The Java Virtual Machine running the web server has crashed due
          to some unexpected reason.  When this happens, the
          /var/log/webconsole/console_debug_log file at the host running
          the web server (as specified by hostname) contains lines
          similar to the following:

          #
          # The exception above was detected in native code outside the VM
          #
          # Java VM: Java HotSpot(TM) Server VM (1.4.1_03-b02 mixed mode)
          #
          # An error report file has been saved as /tmp/hs_err_pid24360.log.
          # Please refer to the file for further information.
          #

    To remedy this, become superuser on the host that was supposed to run the
    web server (as mentioned in hostname) and issue the following command:

      /usr/sbin/smcwebserver restart

* Segmented Files issue.

  Segmented files are not supported on Sun StorEdge QFS shared file systems.

* Stage -n issue.

  The stage(1M) -n option is not supported on Sun StorEdge QFS shared file
  system clients.  The entire file is staged back to the disk cache.

* Bug 4689698.

  When running multiple samfsrestore(1M) commands in a Sun StorEdge QFS
  shared file system, a page lock deadlock can occur and the file system
  in question can hang.  Only the file system for which two
  samfsrestore(1M) commands has been entered is affected.

  To avoid this problem, do not attempt to run two samfsrestore(1M)
  commands at the same time.  To recover from the problem, schedule
  a reboot for the server.

  The problem has never been encountered when running a single
  samfsrestore(1M) command in a Sun SAM-QFS shared file system
  environment, nor has it been seen in an (unshared) Sun SAM-QFS file system.

* Bug 4709129.

  When a metadata device fails (whether because the disk was put
  offline, because Fibre Channel attachment was pulled, etc.),
  the Sun StorEdge QFS file system recognizes the failed I/O, but it can
  leave data in the page and/or buffer cache.  This leftover data
  can be interpreted as a data corruption (ENOCSI) or a page panic.
  Because the timing of such failures is random, several different
  results, one of which is a panic, can occur.

  To avoid this situation, configure a mirror device for the
  metadata partition and/or fix the failing device.  Avoid
  offlining an active metadata device.

* Bug 4877214.

  In a Sun StorEdge QFS shared file system, sparse file reads from
  clients do not zero-fill unwritten blocks.  Instead, clients that
  write a sparse file and read back blocks that they have not written
  might not read zeros.  This affects Sun StorEdge QFS shared clients
  only, not the Sun StorEdge QFS shared metadata server.

Compatibility Issues
====================

The following information pertains to upgrade issues and other
compatibility issues.

 * If you upgrade your Sun StorEdge QFS and Sun StorEdge SAM-FS
   software from a release prior to 4.1 and you use the SAM-QFS
   Manager to make configuration changes, the system creates new
   versions of the mcf, archiver.cmd, and other configuration files.
   If you had comments in your pre-4.1 files, they are removed in the
   new files that result.  SAM-QFS Manager maintains a set of backup
   copies for the configuration files at /etc/opt/SUNWsamfs/.cfg_back.
   It retains the most recent 25 versions of each config file.

 * If you use the SAM-QFS Manager to rename and save an existing
   legacy policy (archive set) by using the Archive Management Tab in
   the SAM-QFS Manager, the content of the archiver.cmd file could be
   substantially different from what you had prior to the save.

 * The SAM-QFS Manager is compatible only with Sun Web Console version
   2.0.2 applications, for example:  Sun StorEdge Enterprise Storage
   Manager 2.1.  Installing this product over any other Sun Web Console
   version will break both applications.

 * Some of the Solaris patches may inadvertently remove the "samsys" line
   from the /etc/name_to_sysnum file when they are installed.  One
   indication of the problem is the message "WARNING: system call missing
   from bind file" appearing in the /var/adm/messages file.  Here's what
   you should do to keep this from causing problems:

   Before installing Solaris patches, save the /etc/name_to_sysnum file:
   # cp /etc/name_to_sysnum  /etc/name_to_sysnum.old

   After installing Solaris patches, check the "samsys" line in the
   old /etc/name_to_sysnum file:
   # grep "samsys /etc/name_to_sysnum.old

   After installing Solaris patches, check the "samsys" line in the
   /etc/name_to_sysnum file:
   # grep "samsys /etc/name_to_sysnum

   If the "samsys" line does not exist in the /etc/name_to_sysnum file,
   add the "samsys" line to the /etc/name_to_sysnum file.  If you are
   using the default Sun StorEdge SAM-FS system call number, do the
   following:
   # echo "samsys 182" >> /etc/name_to_sysnum

   If you are not using the default the Sun StorEdge SAM-FS system call
   number, use the system call number that you selected instead of
   '182' in the above command line.

   You should perform this operation before rebooting after adding the
   Solaris patches.  Otherwise, you will need to perform a second reboot.

 * Beginning with Solaris 9 patch 112233-11, system call number 181 is
   used by Solaris to get information about resource utilization
   (SYS_rusagesys).   The default Sun StorEdge SAM-FS configuration
   was changed in 4.1 to use system call number 182.   You may have a
   different system call number configured if you upgraded from a
   previous release.  In order for the Sun StorEdge SAM-FS and Sun
   StorEdge QFS software to be operational after installing this, or a
   subsequent, Solaris 9 patch, the Sun StorEdge SAM-FS or Sun StorEdge 
   QFS administrator must change the default Sun StorEdge SAM-FS entry
   in /etc/name_to_sysnum from "samsys 181" to an alternate entry,
   like "samsys 182" or "samsys 183", based on the following guidelines:

      The file /etc/name_to_sysnum must contain a "samsys" entry.
      The "samsys" system call number must be unique in /etc/name_to_sysnum
      and not assigned in /usr/include/sys/syscall.h  (Note: entries named
      "SYS_reserved_#" are considered available).  After changing
      /etc/name_to_sysnum a reboot is required.

 * If you create a new file system with the Sun StorEdge QFS 4.1 or Sun
   StorEdge SAM-FS 4.1 software and you want to revert to a 4.0 version,
   you must install Sun StorEdge QFS or Sun StorEdge SAM-FS 4.0 patch -06
   or later.  If you do not install Sun StorEdge QFS or Sun StorEdge
   SAM-FS 4.0 patch -06 or later, you might damage the new file system.
   The Sun QFS and Sun SAM-FS 3.5.0 and earlier systems do not
   support file systems created by the Sun StorEdge QFS or Sun StorEdge
   SAM-FS 4.1 releases.

 * If you are upgrading to the 4.1 releases, or if you plan to downgrade
   from the 4.1 releases, please be aware of the install process.

   4.0 to 4.1 Conversions
   ----------------------
   When upgrading from a 4.0 release to 4.1, pkgadd(1M) checks
   for the presence of the file /etc/opt/SUNWsamfs/LICENSE.4.0 and the absence
   of the file /etc/opt/SUNWsamfs/LICENSE.4.1.  If this is true, the
   system performs the following copies:
   o It copies the script files in /etc/opt/SUNWsamfs and /opt/SUNWsamfs/sbin
     that might have been modified to /etc/opt/SUNWsamfs/scripts.
   o It copies /etc/opt/SUNWsamfs/ftp.cmd to /etc/opt/SUNWsamfs/rft.cmd.

   Conversely, just before a 4.1 package is removed, you can move these files
   back to their pre-4.1 locations by running
   the /opt/SUNWsamfs/sbin/backto40 script.

   If you fall back from 4.1 to 4.0, you must fall back to a 4.0.62
   (patch -06 or later) system.  This is necessary in order for catalog
   conversion to occur.

   You can avoid the conversion from 4.0 to 4.1 by creating the
   /etc/opt/SUNWsamfs/LICENSE.4.1 file or by moving the
   /etc/opt/SUNWsamfs/LICENSE.4.0 file.  The conversion from 4.1 does
   not occur unless the backto40 script is run manually.

   BugId 5027353. The 4.1 shared filesystem uses a different version number for
   the shared hosts file (4 vs. 3).  Roll-forward is automatic, but rollback is
   not. The backto40 script needs to be run for either a SAM-FS/QFS or 
   standalone QFS system if qfs shared filesystems exist. This script will 
   save the hosts file for each shared filesystem so that it can be converted 
   to a version 3 prior to running 4.0. The script only needs to be run on the 
   server which is designated as the server for the shared filesystem, it does
   not need to be run on the clients. Once you have executed the backto40 
   script, you can remove the 4.1 packages and install the 4.0 packages. Once
   the 4.0 package install has been completed, do a "samd config" followed by
   execution of /etc/opt/SUNWsamfs/hosts41to40shared on the server for the
   shared filesystem. This script will convert the hosts file for each shared
   filesystem from a version 4 to a version 3. Once this has been completed,
   execute "samd config" to make sure that the conversion completed, and
   continue with normal system startup for 4.0.

   3.5.0 to 4.1 Conversions
   ------------------------
   When upgrading from a 3.5.0 release to 4.1, pkgadd(1M) checks
   for the presence of the file /etc/opt/LSCsamfs/mcf and the absence
   of the file /etc/opt/SUNWsamfs/mcf.  If this is true, the system
   performs the following copies:

   o It copies the configuration files in /etc/opt/LSCsamfs to
     /etc/opt/SUNWsamfs.

   o It copies scripts that might have been modified to
     /etc/opt/SUNWsamfs/scripts for comparison with the new versions.

   Conversely, just before a 4.1 package is removed, you can move the files
   in /etc/opt/SUNWsamfs and /var/opt/SUNWsamfs back to
   /etc/opt/LSCsamfs and /var/opt/LSCsamfs by running the
   /opt/SUNWsamfs/sbin/backto350 script.

   If you fall back from 4.1 to 3.5.0, you must fall back to a 3.5.0.81
   or later system.  This is necessary in order for catalog conversion
   to occur.

   You can avoid the conversion to 4.1 from 3.5.0 moving the
   /etc/opt/LSCsamfs/mcf file.  The conversion from 4.1 does
   not occur unless the backto350 script is run manually.

   Subsequent paragraphs in this release note contain more information
   about the directory reorganization and catalog re-design.

 * Conversion of /etc/opt/LSCsamfs/samlogd.cmd when upgrading from 3.5.0

   The staging code in 3.5.0 has been replaced by a new stager daemon
   in release 4.0.  If you had stage logging directives in
   /etc/opt/LSCsamfs/samlogd.cmd, you must add the equivalent directives
   to /etc/opt/SUNWsamfs/stager.cmd to have the same logging
   functionality under the Sun SAM-FS 4.0 release.

   If your /etc/opt/LSCsamfs/samlogd.cmd file looked like this, for example:

     stage=/var/opt/SUNWsamfs/log/stager start

   You should have the following in /etc/opt/SUNWsamfs/stager.cmd:

     logfile = /var/opt/SUNWsamfs/log/stager

   For more information, see the stager.cmd(4) man page.

 * If you plan to enable the Sun SAN-QFS file system, verify that you have
   Tivoli SANergy File Sharing software at release level 2.2.3.  For more
   information about the SAN-QFS file system, see the Sun StorEdge QFS
   and Sun StorEdge SAM-FS File System Administration Guide.

 * The 'queuedir =' and 'datadir =' directives are no longer supported in
   the archiver.cmd file.  These directives must be removed.  If these
   directives are not removed, an error message is generated and the
   archiver does not run.

   The archiver queue files are written to the following directory:

   /var/opt/SUNWsamfs/archiver/Queues

   The archiver data directory is as follows:

   /var/opt/SUNWsamfs/archiver

 * A change in directory structure, called directory entry hash, was
   made to SAM-FS, SAM-QFS and QFS standalone at SAM-FS 3.5.0.  A 16-bit
   hash value was implemented in a previously unused field within the
   directory structure.  However, testing discovered that in early
   SAM-FS file systems (version 3.0.X and previous), this field was
   already used.

   When upgrading from one of these early file systems to 4.1, this
   problem could manifest itself as "No such file or directory entry"
   when using sfind(1) or sls(1).

   Because of this problem, and for general performance enhancement
   reasons, it is strongly recommended that a site upgrading to 3.5.0
   or higher run the following:

      samfsck -F -G family_set_name

   This should be performed on each upgraded file system.

 * Sun SAM-Remote 4.1 is incompatible with SAM-Remote 3.3.1 and SAM-Remote
   3.3.0. This is because of the SAM-FS 3.5.0 catalog re-design.
   The same version of SAM-Remote must be installed on SAM-Remote
   clients and servers.

 * The Sun StorEdge SAM-FS 4.1 release removed support for Ampex 410,
   810 and 914 tape libraries and for Ampex tapes and the Ampex DST driver.

 * A new license scheme was implemented in the 4.0 releases.

   - Sites upgrading from 3.5.0 (or earlier releases) to 4.1 must have
     a set of new license keys supplied by their Authorized Service
     Provider (ASP) or Sun Microsystems, Inc.  Put the keys in file
     /etc/opt/SUNWsamfs/LICENSE.4.1.  The samu(1M) license "l" display
     allows you to view the products for which the system is licensed.

   - Sites upgrading from 4.0 to 4.1 do not need a new set of license
     keys.  The upgrade process automatically copies the LICENSE.4.0
     file to LICENSE.4.1 file. The 4.0 license is valid with the 4.1
     release.

     NOTE: If you made changes to your site's configuration
     during the upgrade procedure, you might need a new license in
     order for the configuration changes to work correctly.

   Some notes about licensing:

   - To get a temporary license, go to the following web site:

     www.lsci.com/licensestart.sun

   - The license is divided into two logical sections:  system and media.
     The system license licenses the host, expiration date, and the
     Sun StorEdge SAM-FS features.  The media licenses a robot type and
     media type pair.  This is tied to the system license by hostid.
     The number of media slots for the media type and robot type are
     kept here.

   - If the license is missing, is corrupted, has an incorrect hostid,
     or has expired, the license will be regarded as expired or corrupt.
     This means that the system will no longer allow file system mounts,
     media mounts, or staging.

     If the number of slots in use exceeds the licensed number, the
     license is regarded as suspended.  This means that the system will
     no longer allow media mounts, labelling new media, staging, or
     importing media.  Relabeling of old media is still allowed if the
     license is suspended.

     For both conditions, media mounts are not allowed and archiving
     does not occur as long as the condition exists.

     Because exporting is still allowed in the suspended condition,
     exporting enough media to bring the number of slots in use back
     into conformance with the license clears the suspended condition.


Required Solaris Patches
========================

The patches listed below can be obtained from Sun.
Refer to the Sun Microsystems web page for a list of recommended patches:

    http://sunsolve.Sun.COM/pub-cgi/show.pl

All of our testing was done with the patches at the revision level shown:

 * The Sun StorEdge QFS and Sun StorEdge SAM-FS software for Solaris 8
   installations require Solaris 8 Update 5 (Solaris 8 07/01) if using
   the Sun StorEdge QFS shared file system feature.

 * The Sun StorEdge SAM-FS software needs the following patches installed
   when running with Solaris 2.8:

       108528-02 kernel update patch for hot swappable hardware support only

 * The Sun StorEdge SAM-FS software needs the following patches installed
   when running with Solstice DiskSuite 4.1:

       104172-24 Solstice DiskSuite 4.1 product patch

 * The Sun StorEdge SAM-FS software needs the following patches installed
   when running with Solstice DiskSuite 4.2:

       106627-11 Solstice DiskSuite 4.2 product patch

 * The Sun StorEdge SAM-FS software needs the following patches installed
   when running with Fibre Channel tape drives:

       111095-06 SunOS 5.8: fctl/fp/fcp/usoc driver patch

 * The Sun StorEdge SAM-FS software needs the following patches installed
   when the X6757A SBus Fibre Channel HBA is used to access either tape
   drives or libraries:

       112244-02 SunOS 5.8: Hardware/FCode: SBus Dual Fibre Channel Host Adapter


LEGAL NOTICES
=============

Copyright 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to
license terms.  Third-party software, including font technology, is
copyrighted and licensed from Sun suppliers.  Portions may be derived from
Berkeley BSD systems, licensed from U. of CA.  Sun, Sun Microsystems, the
Sun logo, Solaris, and Sun StorEdge are trademarks or registered trademarks
of Sun Microsystems, Inc. in the U.S. and other countries.  All SPARC
trademarks are used under license and are trademarks or registered
trademarks of SPARC International, Inc. in the U.S. and other countries.
Federal Acquisitions: Commercial Software - Government Users Subject to
Standard License Terms and Conditions.

Copyright 2004 Sun Microsystems, Inc.  Tous droits reserves.  Distribue par
des licences qui en restreignent l'utilisation.  Le logiciel detenu par des
tiers, et qui comprend la technologie relative aux polices de caracteres,
est protege par un copyright et licencie par des fournisseurs de Sun.  Des
parties de ce produit pourront etre derivees des systemes Berkeley BSD
licencies par l'Universite de Californie.  Sun, Sun Microsystems, le logo
Sun, Solaris, et Sun StorEdge sont des marques de fabrique ou des marques
deposees de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilisees sous licence et sont des marques de
fabrique ou des marques deposees de SPARC International, Inc. aux Etats-Unis
et dans d'autres pays.

