[VTL与磁带系统] 磁带的问题,还是带库的问题?如何手工清洗带库的drive [复制链接]

论坛徽章:: 0

发表于 2004-11-26 15:20 |显示全部楼层

veritas netbackup 4.5 fp3 + hp-ux + oracle
备份作业在执行作业的时候,发生media position的错误,然后就在mail中报告如下:如何分析这个出错的mail,可能是磁带坏了,还是带库需要清洗了,如何进行带库的清洗?
# mail
From root@hr02 Fri Nov 26 15:07:55 EAT 2004
Received: (from root@localhost)
      by hr02 (8.9.3/8.9.3) id PAA26638;
      Fri, 26 Nov 2004 15:07:54 +0800 (EAT)
Date: Fri, 26 Nov 2004 15:07:54 +0800 (EAT)
Message-Id: <200411260707.PAA26638@hr02>;
To: root@hr02
From: root@hr02
Subject: hr02: Event Monitor Notification

>;------------ Event Monitoring Service Event Notification ------------<

Notification Time: Fri Nov 26 15:07:54 2004

hr02 sent Event Monitor notification information:

/storage/events/tapes/SCSI_tape/0_0_10_0_0.2.25.255.0.0.2
is >;= 3.
Its current value is CRITICAL(5).

Event data from monitor:

Event Time..........: Fri Nov 26 15:07:54 2004
Severity............: CRITICAL
Monitor.............: dm_stape
Event #.............: 100243
System..............: hr02

Summary:
   Tape at hardware path 0/0/10/0/0.2.25.255.0.0.2 : Media failure

Description of Error:

   The device was unsuccessful in reading data for the current I/O request
   because it could not find the requested recorded entity on the medium. The
   request may have been processed in a way which could cause damage to or
   loss of data.

   For furthur isolation of the problem, it may be possible that the
   combination of values of Sense Code, Sense Qualifier and Sense Key may be
   vendor specific. In that case, please contact the manufacturer of the
   device. It may also be possible that the combination of SCSI Sense
   Code/Qual/Key was not intended to be used by this type of device.

Probable Cause / Recommended Action:

   Reformatting the medium may fix the problem.

   Alternatively, the medium in the device is flawed. If the medium is
   removable, replace the medium with a fresh one.

   Alternatively, if the medium is not removable, the device has experienced
   a hardware failure. Contact your HP support representative to have the
   device checked.

Additional Event Data:
   System IP Address...: 172.20.4.89
   Event Id............: 0x41a6d64a00000000
   Monitor Version.....: B.01.05
   Event Class.........: I/O
   Client Configuration File...........:
   /var/stm/config/tools/monitor/default_dm_stape.clcfg
   Client Configuration File Version...: A.01.00
      Qualification criteria met.
            Number of events..: 1
   Associated OS error log entry id(s):
      0x41a6d64a00000000
   Additional System Data:
      System Model Number.............: 9000/800/rp7410
      OS Version......................: B.11.11
      System Firmware Version.........: 16.11
      System Serial Number............: SGH43241LS
      System Software ID..............: 729066710
      EMS Version.....................: A.03.20
      STM Version.....................: A.35.00
      System Current Product Number...: A6752A
      System Original Product Number..: A6752A
   Latest information on this event:
      http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100243

v-v-v-v-v-v-v-v-v-v-v-v-v D  E  T  A  I  L  S v-v-v-v-v-v-v-v-v-v-v-v-v

Component Data:
   Physical Device Path....: 0/0/10/0/0.2.25.255.0.0.2
   Inquiry Vendor ID.......: HP
   Inquiry Product ID......: Ultrium 1-SCSI
   Firmware Version........: E38W
   Serial Number...........: HU73A02465

Product/Device Data:

   Logger ID.........: stape
   Product Identifier: SCSI Tape
   Product Qualifier.: HPUltrium
   SCSI Target ID....: 0x00
   SCSI LUN..........: 0x02

I/O Log Event Data:

   Driver Status Code..................: 0x00000005
   Length of Logged Hardware Status....: 26 bytes.
   Offset to Logged Manager Information: 32 bytes.
   Length of Logged Manager Information: 30 bytes.

Hardware Status:

   Raw H/W Status:
      0x0000: 00 00 00 02 F0 00 03 00 00 00 6B 0E 00 00 00 00
      0x0010: 14 00 00 00 50 90 00 00 00 00

   SCSI Status...: CHECK CONDITION (0x02)
      Indicates that a contingent allegiance condition has occurred.  Any
      error, exception, or abnormal condition that causes sense data to be
      set will produce the CHECK CONDITION status.

SCSI Sense Data:

   Undecoded Sense Data:
      0x0000: F0 00 03 00 00 00 6B 0E 00 00 00 00 14 00 00 00
      0x0010: 50 90 00 00 00 00

   SCSI Sense Data Fields:
      Error Code                   : 0x70
      Segment Number                : 0x00
      Bit Fields:
            Filemark                : 0
            End-of-Medium             : 0
            Incorrect Length Indicator : 0
      Sense Key                      : 0x03
      Information Field Valid       : TRUE
      Information Field             : 0x0000006B
      Additional Sense Length       : 14
      Command Specific             : 0x00000000
      Additional Sense Code          : 0x14
      Additional Sense Qualifier    : 0x00
      Field Replaceable Unit       : 0x00
      Sense Key Specific Data Valid : FALSE
      Sense Key Specific Data       : 0x00 0x50 0x90

      Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated
      with a nonrecovered error condition that was probably caused by a
      flaw in the medium or an error in the recorded data.  This sense key
      may also be returned if the device is unable to distinguish between a
      flaw in the medium and a specific hardware failure (sense key 0x04).

      The combination of Additional Sense Code and Sense Qualifier (0x1400)
      indicates: Recorded entity not found.

SCSI Command Data Block:  (not present in log record)

Manager-Specific Information:

   Raw Manager Data:
      0x0000: 04 3B 03 2A 00 00 00 00 00 00 00 02 00 00 00 00
      0x0010: 04 00 02 16 FE 00 00 06 11 01 00 00 6C 00

>;---------- End Event Monitoring Service Event Notification ----------<

?

如果是磁带坏了,那这个磁带上的东西都没用了,也太容易坏掉了.现在,我只能先手工将这盘磁带frozen掉,先将数据备份到新的磁带上去?不知道这样处理是否比较合理?

备份, 磁带, 备份, 磁带