sam-shrink(1M)

NAME
     sam-shrink - Sun QFS and SAM-QFS disk space shrink process

SYNOPSIS
     /opt/SUNWsamfs/util/sam-shrink  file_system   |   family_set
     -remove | -release eq

AVAILABILITY
     SUNWqfs

     SUNWsamfs

DESCRIPTION
     This sam-shrink process is executed when a shrink of  a  Sun
     QFS  or SAM-QFS file system is required.  The samadm command
     eq-remove or  eq-release  or  the  samu  command  remove  or
     release cause the state of the specified device to be set to
     noalloc. Then, the file system requests  the  master  daemon
     sam-fsd to start the process sam-shrink.  The specified dev-
     ice (eq) must be a data device that resides within a ma file
     system.   If the data device is a stripe group, the first eq
     of the stripe group must be  specified.   The  eq  state  is
     changed  to noalloc before sam-shrink is started. This means
     there will be no more allocation on this device.

     The  sam-shrink  command  should  not  be  executed  by  the
     administrator  separately.  Pre and post processing that the
     SAM-QFS file system does automatically is  necessary  for  a
     successful shrink.

     The remove option copies all data that reside on eq  to  the
     other  available data devices according to the mount parame-
     ters.  Note, if eq is a stripe group, another  stripe  group
     must be available with the same number of devices.

     The release option is only available on a SAM-QFS  archiving
     file  system. The release option marks all files that reside
     on eq offline. If any files have partial on-line, that  data
     will  be  released, too.  The release will fail if there are
     any files that have not been archived. The release will also
     fail  if  there  are  any  files  that  are staging or being
     archived. If the release command fails, you may execute  the
     release command again to release any newly achived files. If
     there are files that cannot be archived, then you  may  exe-
     cute  the remove command to move the data that resides on eq
     to the other available data devices according to  the  mount
     parameters.

     After successful completion of the remove or release  opera-
     tion,  the  eq state will be off. It may take a long time to
     complete the release operation and an even  longer  time  to
     complete the  remove operation.  You can monitor the logfile

     and/or the /var/opt/SUNWsamfs/trace/sam-shrink file to check
     the status.

     If the remove or release operation was not able  to  release
     or move all the files on the eq, the state will remain noal-
     loc. The remove or release operation can be  executed  again
     on  this  eq.  The shrink.log should be examined for reasons
     why the eq state could not be changed to off.

LOG
     Within the shrink.cmd file, you can specify a log  file  for
     each Sun QFS or SAM-QFS file system.  If no logfile=filename
     directive exists in the file, no logging occurs.   For  more
     information  on  the  logfile=filename  directive,  see  the
     shrink.cmd(4) man page.

     The sam-shrink process creates the log file if it  does  not
     exist.  The following example shows the log file entries for
     a release command followed by a remove command.

          Tue Sep 29 15:31:15 2008 Shrink process started: samfs5 release 15
          RE 6412.5  P S0 /sam1/250m
          RE 5131.5  P S0 /sam1/filecq
          NA 5095.4 -- S0 /sam1/filecu
          ER 5039.5 16 S0 /sam1/filedi
          NA 5039.2 -- S0 /sam1/lsc/filexx
          Tue Sep 29 15:31:55 2008 shrink process unsuccessful for samfs5 eq 15:
          busy files=1, unarchived files=2, total_errors=1
          Tue Sep 29 15:32:15 2008 Shrink process started: samfs5 remove 15
          MV 5095.4 -- S0 /sam1/filecu
          MV 5039.5 -- S0 /sam1/filedi
          MV 5039.2 -- S0 /sam1/lsc/filexx
          Tue Sep 29 15:33:21 2008 shrink process successful for samfs5 eq 15

     The first line shows the arguments with which the shrink was
     invoked: file_system command equipment.

     The next block of lines has one  line  per  file  processed:
     The fields are as follows:

     Field Number   Content

     1              This  field  contains  the   tag:    RE   for
                    released,   MV   for   removed,  NA  for  not
                    archived, or ER for error releasing or remov-
                    ing file.  If the directive do_not_execute is
                    set in the shrink.cmd file, this  field  con-
                    tains the tag: NO.

     2              This field contains the inode and  generation
                    number of the file.

     3              This field contains the stage or  errno  tag.
                    For the release command, tag is either  S for
                    file staged  back  on-line,   P  for  partial
                    staged  back  on-line,  or  --  for  no stage
                    action on this file.  For a field with ER  in
                    the  first  field,  this  tag  is  the  error
                    number.

     4              This field contains an S followed by the seg-
                    ment  number.  This is the number of the seg-
                    ment that was released.

     5              This field contains the full path name of the
                    released or moved file.

SEE ALSO
     mcf(4).  shrink.cmd(4).