| Title: | AdvFS Support/Info/Questions Notefile |
| Notice: | note 187 is Freq Asked Questions;note 7 is support policy |
| Moderator: | DECWET::DADDAMIO |
| Created: | Wed Jun 02 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1077 |
| Total number of notes: | 4417 |
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: How To Recognize & Recover from AdvFS corruption.
DATE:
AUTHOR: John Donovan TD #:
DTN: 381-1344
ENET: guru::donovan CROSS REFERENCE #'s:
DEPARTMENT: UNIX Support Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: All PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
INTRODUCTION:
Recently several customer escalations to DIGITAL UNIX have been sent
to engineering regarding data corruption in AdvFS.
PROBLEM:
After careful examination, it became apparent that recovery procedures
were not adequately documented resulting in undue escalations
RESOLUTION/WORKAROUND:
This has resulted in DIGITAL UNIX documenting how to recover from
AdvFS failures. The new "AdvFS How to recover from failure" web pages
can be found at:
http://www.zk3.dec.com/useg/tech_info/filesystem/advfs_howto.html
Note: This is Under construction and will be updated every so often!
ADDITIONAL COMMENTS:
The above web page should be checked every so often for changes so
that current methods will always be in use.
*** DIGITAL INTERNAL USE ONLY ***
\\ GRP=TIME_DEPENDENT CAT=HARDWARE DB=CSSE_TIME_CRITICAL
\\ TYPE=KNOWN_PROBLEM TYPE=BLITZ STATUS=CURRENT
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1074.1 | Sparse file corruption blitz | KITCHE::schott | Eric R. Schott USG Product Management | Thu Jun 05 1997 11:13 | 70 |
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: ADVFS DATA CORRUPTION ON SPARSE FILE WRITES
DATE:4 June 1997
AUTHOR: John Donovan TD #:
DTN: 381-1344
ENET: guru::donovan CROSS REFERENCE #'s:
DEPARTMENT: UNIX Support Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: All PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
INTRODUCTION:
An AdvFS data corruption problem has been found in our DIGITAL
UNIX test environment.
PROBLEM:
An AdvFS data corruption problem has been found in our V4.0 test
environment. The corruption may occur when a user program writes
to sparse files. AdvFS does not panic as a result of this problem
and the AdvFS verify utility doesn't detect the problem.
The corruption can be detected only by inspection of user data.
RESOLUTION/WORKAROUND:
The solution consists of a fix to AdvFS to not cause the corruption,
and a fix to the verify utility to detect it and to help in the
recovery of the corrupted data. DIGITAL UNIX Engineering strongly
recommends that these patches be applied.
The official fix for this problem is being packaged as part of the
next patch kit release for the following releases:
V4.0, V4.0A, V4.0B
Until these are available, a pre-release patch is available:
guru.zk3.dec.com:/usr/guest/misc/osf/MCPM11AX5/v4.0_bl5/v4.0_bl5.tar.Z
v4.0a_bl5/v4.0a_bl5.tar.Z
v4.0b_bl5/v4.0b_bl5.tar.Z
These patches require prior installation of the Digital Unix
Patch Kits.
Patch Kit-0002 for Digital Unix V4.0 and V4.0A, Patch Kit-0003
for Digital Unix V4.0B. Please refer to the setld patch kit
Release Notes to determine which patch kit is currently installed
on your system and for Patch Kit Installation Instructions.
ADDITIONAL COMMENTS:
*** DIGITAL INTERNAL USE ONLY ***
\\ GRP=TIME_DEPENDENT CAT=HARDWARE DB=CSSE_TIME_CRITICAL
\\ TYPE=KNOWN_PROBLEM TYPE=BLITZ STATUS=CURRENT
| |||||