logo

Manual Pages

Table of Contents

NAME

na_sis - Log of Advanced Single Instance Storage (SIS) activities

SYNOPSIS

/etc/log/sis

DESCRIPTION

The sis log file contains a log of SIS activities for this filer. The file lives in /etc/log on the root volume.

Every Sunday at midnight, /etc/log/sis is moved to /etc/log/sis.0; /etc/log/sis.0 is moved to /etc/log/sis.1; and so on. The suffix can go up to 5, so the old /etc/log/sis.5 will be deleted. SIS activities are saved for a total of seven weeks.

Each entry of the /etc/log/sis file is a single line containing the following space-separated fields.

  timestamp path event_info

The following is a description of each field.

timestamp
Displayed in ctime() format, e.g. Fri Jul 17 20:41:09 GMT. Indicates the time this event was recorded.

path
The full path to a SIS volume as shown below: 
  /vol/volume_name

event_info
The event which is being logged. Some events may have extra information in parentheses. The current event types are:

Begin [ ( scan | check | snapvault | user ) ] When a SIS operation is first kicked off. There are multiple cases for a SIS operation. If the operation is not started by scheduler, the event is augmented with the following additional information in parenthesis.

scan Corresponds to "sis start -s", when we are instructed to scan the entire file system for duplicated blocks.

check If we are specifically instructed to perform fingerprint database checking.

snapvault
If the snapvault initiated the SIS operation.

user
When the SIS operation is kicked off with CLI or ZAPI.

Undo
Corresponds to "sis undo" command.

End ( processed_size KB )
When a long-running SIS operation (either Begin or Undo) completes successfully. We should include the size of data processed in the event.

Error ( Error_message )
If a SIS operation aborts or fails to start, we should indicate the cause of the error.

Config ( schedule_string )
When a "sis config" command successfully set or modified the SIS schedule on a volume. The new schedule string is logged with the event.

Enable When the SIS is enabled on a volume.

Disable
When the SIS is disabled on a volume.

EXAMPLE

A SIS operation initiated by schedule and based on change log is the most common case and thus considered the default. On the successful completion of such an operation, the log file should have the following entries: 

  Tue Jul 12 02:01:05 GMT    /vol/dense_vol        Begin
  Tue Jul 12 02:02:22 GMT    /vol/dense_vol        End (2356080 KB)

If the SIS operation falls into one of the four cases listed above, the Begin event entries would look rather like: 

  Tue Jul 12 02:01:05 GMT    /vol/dense_vol        Begin  (scan)
  Tue Jul 12 02:01:05 GMT    /vol/dense_vol        Begin  (check)
  Tue Jul 12 02:01:05 GMT    /vol/dense_vol        Begin  (snapvault)
  Tue Jul 12 02:01:05 GMT    /vol/dense_vol        Begin  (user)

If a SIS operation aborts, the Error event will replace the End event. 

  Fri Jul 15 00:40:31 GMT    /vol/dense_vol        Begin
  Fri Jul 15 18:58:26 GMT    /vol/dense_vol        Error (Volume is full)

The Undo is the only other long-running event, similar to the Begin event, is terminated by either End or Error. 

  Fri Jul 15 18:58:26 GMT    /vol/dense_vol        Undo

The Enable, Disable and Config events are only logged when they complete successfully. 

  Fri Jul 15 18:58:26 GMT    /vol/dense_vol        Enable
  Fri Jul 15 18:58:26 GMT    /vol/dense_vol        Disable
  Fri Jul 15 18:58:26 GMT    /vol/dense_vol        Config (sun-sat@0-23)

FILES

/etc/log/sis
SIS log file for current week.

/etc/log/sis.[0-5] SIS log files for previous weeks.

SEE ALSO

  na_sis(1)

Table of Contents