NAME

devlog - Device log file

SYNOPSIS

∕var∕opt∕SUNWsamfs∕devlog∕nn

AVAILABILITY

SUNWsamfs

DESCRIPTION

In Oracle HSM environments, media or tape hardware events that require operator intervention (such as tape positioning errors and requests for cleaning) are logged to file in the following directory:

∕var∕opt∕SUNWsamfs


Within the preceding directory, events are logged to files
that are named for the devices listed in the mcf file.
For example, file devlog∕47 logs all events for the
device identified by Equipment Number 47 in the mcf file.

After an event is logged, you can use the tapealert (1m)
command to read the event logged in the devlog∕nn file,
interpret the event, and write it to a text file for easier viewing.
For more information about the specific events logged to the
device log files, see the tapealert (1m) man page.

The tapealert (1m) command logs the following two types
of messages in the device log (devlog∕nn) file:



Device TapeAlert support 



Active TapeAlert flags



The preceding type of messages are the undecoded TapeAlert events.  The
tapealert (1m) command decodes these messages into a more
readable format.
Device Support TapeAlert Log Messages
The undecoded device log messages 
for device support contain the
following information:



Field 1 displays the date in year∕month∕day format.



Field 2 displays the time expressed in a 24-hour clock format.



Field 3 displays the message number, followed by TapeAlert
and supported.

TapeAlert messages start at 12000.




The following is an example of a device support message:

2003∕06∕13 10:52:23 12001 TapeAlert supported


Active Tape Alert Flags
The device log messages for active TapeAlert flags contain
the following information:



Field 1 displays the date in year∕month∕day format.



Field 2 displays the time expressed in a 24-hour clock.



Field 3 displays the message number, followed by TapeAlert.

TapeAlert messages start at 12000.





Field 4 displays the characters eq= followed by
the mcf (4) equipment number. 



Field 5 displays the characters type= followed by
the inquiry  peripheral device type.



Field 6 displays the characters seq= followed by
the sysevent sequence number.
The sysevent sequence number is zero if
the sysevent_post_event function fails
or is not called.
The sysevent event handler $sequence macro
is the same as the
devlog∕nn file's seq=n number.



Field 7 displays the characters len= followed by the number of
valid TapeAlert flags.



Field 8 displays the flags field.
The 64 TapeAlert flags are written in big endian format.
The most significant bit, on the left, is flag 64.
The least significant bit is flag 1.



The following is an example of a TapeAlert flags message:

2003∕06∕13 10:52:23 12006 TapeAlert eq=91 type=1 seq=8 len=50 flags=0x0002004000000000

A decoded TapeAlert flag consists of four parts:



Flag



Severity



Application message



Probable cause




The T10 Technical Committee
defines three types of flags.  Table 1 lists these flags
in order of increasing severity.


Table 1.  Flag Types



Severity Urgent Intervention Risk of Data Loss Explanation




Critical X X  

Warning   X X


Information     X



If an Information-level flag is issued, you can perceive it as a
predicted failure.  Take the time to correct the problem before it
worsens.

The tapealert (1m) command supports the minimum flag subset
as defined by the T10 Committee.  Table 2 shows these flags.


Table 2.  Tape Drive TapeAlert Flags - Minimum Subset



Flag Number Type Active Inactive




3h Hard error Active for any unrecoverable read, write, or positioning error, as specified in flag number 5h and 6h. Internally deactivated when the media is unloaded.


4h Media Active for any unrecoverable read, write, or positioning error that is due to faulty media. Internally deactivated when the media is unloaded.


       

5h Read failure Active for any unrecoverable read error where the diagnosis is uncertain and could either be faulty media or faulty drive hardware. Internally deactivated when the media is unloaded.


       

6h Write failure Active for any unrecoverable write or positioning error where the diagnosis is uncertain and could either be faulty media or faulty drive hardware. Internally deactivated when the media is unloaded.


       

14h Clean now Active when the tape drive detects a cleaning cycle is needed. Internally deactivated when the tape drive is successfully cleaned.


       

16h Expired cleaning Active when the tape drive detects a cleaning cycle was attempted but was not successful. Internally deactivated when the next cleaning cycle is attempted.


       

1fh Hardware B Active when the tape drive fails its internal Power-On-Self-Tests (POST). Not internally deactivated until the drive is powered off.




Table 3 summarizes the errors in the devlog∕nn file.


Table 3. TapeAlert Flags for Tape Drives With or Without an Autoloader, Grouped by Purpose



Start of Range End of Range Purpose of this Range of Flags




01h 13h Tape drive write∕read management


14h 19h Cleaning management


1Ah 27h Tape drive hardware errors


28h 31h Tape autoloader errors


32h 40h Further tape errors



The information in tables 1, 2, and 3 is derived from
SCSI Stream Commands - 2 (SSC-2), Revision 08d.

Table 1. Flag Types
Severity	Urgent Intervention	Risk of Data Loss	Explanation
Critical	X	X
Warning		X	X
Information			X

Table 2. Tape Drive TapeAlert Flags - Minimum Subset
Flag Number	Type	Active	Inactive
`3h`	Hard error	Active for any unrecoverable read, write, or positioning error, as specified in flag number `5h` and `6h`.	Internally deactivated when the media is unloaded.
`4h`	Media	Active for any unrecoverable read, write, or positioning error that is due to faulty media.	Internally deactivated when the media is unloaded.

`5h`	Read failure	Active for any unrecoverable read error where the diagnosis is uncertain and could either be faulty media or faulty drive hardware.	Internally deactivated when the media is unloaded.

`6h`	Write failure	Active for any unrecoverable write or positioning error where the diagnosis is uncertain and could either be faulty media or faulty drive hardware.	Internally deactivated when the media is unloaded.

`14h`	Clean now	Active when the tape drive detects a cleaning cycle is needed.	Internally deactivated when the tape drive is successfully cleaned.

`16h`	Expired cleaning	Active when the tape drive detects a cleaning cycle was attempted but was not successful.	Internally deactivated when the next cleaning cycle is attempted.

`1fh`	Hardware B	Active when the tape drive fails its internal Power-On-Self-Tests (POST).	Not internally deactivated until the drive is powered off.

Table 3. TapeAlert Flags for Tape Drives With or Without an Autoloader, Grouped by Purpose
Start of Range	End of Range	Purpose of this Range of Flags
`01h`	`13h`	Tape drive write∕read management
`14h`	`19h`	Cleaning management
`1Ah`	`27h`	Tape drive hardware errors
`28h`	`31h`	Tape autoloader errors
`32h`	`40h`	Further tape errors



SEE ALSO
tapealert (1m).

mcf (4).