ATTO Technology Express SAS R348 Anleitung zur Fehlerbehebung Seite 6

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 9
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 5
of controller.
B.) Error Log Capabilities
The ATTO ExpressSAS Driver does not use the system log to communicate driver
events to the user. The system log has very limited resources and events are easily
lost. Instead, the driver logs events internally until they are retrieved using the
ATTOExpressSASRaid log utility.
Although the number of events can never be predicted, the driver's internal event log
should be large enough to hold all events from initial driver loading until
ATTOExpressSASRaid log can be run. Should the event log become full, the driver will
continue logging events while overwriting the earliest previously logged events. In other
words, the event log will always be full with the most recent events. If event data has
been lost, ATTOExpressSASRaid log will display "...Lost X bytes..." where X is the
number of bytes lost.
The ATTOExpressSASRaid log utility will continuously display events as they are logged
by the driver. You can set the utility as a Startup Item to always retrieve events in the
background; however, this may result in a small degradation in performance.
Once events are retrieved and displayed, they can not be displayed again even if they
are not overwritten by future events. To keep the events for future reference, save the
terminal output or use standard redirection when starting ATTOExpressSASRaid log to
save the output to a file.
Each event begins with a channel identifier, Channel X.Y.Z, where X is the PCI bus
number, Y is the PCI device number and Z is the PCI function number. Additional driver
initialization messages may be logged before this information is available.
You can control the types of events that are logged via the -e System NVRAM option.
See Section A for instructions on how to set this option. Each bit in the mask
corresponds to a group of related messages. The following bits are currently defined:
0x01 Log fatal events that prohibit the driver from loading normally.
0x02 Log events associated with the ExpressSAS Raid controllerloop.
0x04 Log SCSI request errors.
0x08 Log events reported by the controller chip.
0x10 Log port login/logout events.
0x20 Log RSCN events.
Page 6 of 9 ATTO Technology, Inc. July 12, 2007
Seitenansicht 5
1 2 3 4 5 6 7 8 9

Kommentare zu diesen Handbüchern

Keine Kommentare