| Skip Navigation Links | |
| Exit Print View | |
|
Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
1. User Commands (Man Pages Section 1)
2. Maintenance Commands (Man Pages Section 1M)
3. Library Functions (Man Pages Section 3)
4. Library Functions (Man Pages Section 3X)
5. File Formats (Man Pages Section 4)
NAME
devlog - Device log file
SYNOPSIS
/var/opt/SUNWsamfs/devlog/nn
AVAILABILITY
SUNWsamfs
DESCRIPTION
In SAM-QFS 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:
o Device TapeAlert support
o 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. The undecoded device log
messages for device support contains the following
information:
Field Content
1 The date in year/month/day format.
2 The time expressed in a 24-hour clock.
3 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
The device log messages for active TapeAlert flags contain
the following information:
Field Content
1 The date in year/month/day format.
2 The time expressed in a 24-hour clock.
3 The message number, followed by TapeAlert.
TapeAlert messages start at 12000.
4 The characters eq= followed by the mcf(4)
equipment number.
5 The characters type= followed by the inquiry
peripheral device type.
6 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.
7 The characters len= followed by the number of
valid TapeAlert flags.
8 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:
1. Flag
2. Severity
3. Application message
4. 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 Explanation
3h, Hard error Active for any unrecoverable
read/write/positioning error.
Internally deactivated when the media is
unloaded. This flag is active as
specified in flag number 5h and 6h.
4h, Media Active for any unrecoverable
read/write/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/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 Flag Definition Groupings for Tape
Drives With or Without an Autoloader
Flag Number(s) Definition
01h to 13h Tape drive write/read management
14h to 19h Cleaning management
1Ah to 27h Tape drive hardware errors
28h to 31h Tape autoloader errors
32h to 40h Further tape errors
The information in tables 1, 2, and 3 is derived from SCSI
Stream Commands - 2 (SSC-2), Revision 08d.
SEE ALSO
tapealert(1M).
mcf(4).
|