Solaris/Veritas Not Reporting Bad Blocks

From: Mark Hargrave (hargrme@wisdom.maf.nasa.gov)
Date: Wed Apr 17 2002 - 07:54:06 EDT


I have a situation where our ORACLE database reported corrupt data
block on a particular file system, but Solaris and Veritas reported
nothing.

This is the error from ORACLE:

Reread of blocknum=10348, file=/optp06/oradata/optp/users01.dbf. found same
corrupt data
The trace file generated today, does indicate corruption:
Corrupt block relative dba: 0x004009cf (file 1, block 2511)
Bad check value found during buffer read Data in bad block - type: 6
format: 2 rdba: 0x004009cf
last change scn: 0x0000.00028efe seq: 0x1 flg: 0x04 consistency value in
tail: 0x8efe0601
check value in block header: 0xca7e, computed block checksum: 0x304 spare1:
0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x004009cf (file 1, block 2511) found same corrupted data

I ran a fsck from Veritas VM on the file system in question and it
reported no errors. ORACLE's response to the problem was to build another
file system and move the data, which did correct the problem.
-------------------------------------------------------------------------
Questions:
---------

1. Why didn't Veritas VM or FS report any bad block problems?

2. Is there a tool/utility that will do a more through checkout of
   the file system?
-------------------------------------------------------------------------

System/Software info:

H/W: TATUNG E450
Solaris: 2.8 with latest patches
Veritas VM: 3.1

Thanks,

Mark

-----------------------------------------------------
Mark Hargrave, Sr. Unix Systems Administrator
Lockheed Martin Space Systems Co. - Michoud Operations
New Orleans, LA

E-Mail: hargrme@wisdom.maf.nasa.gov
-----------------------------------------------------
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:13 EDT