HP3000-L Archives

April 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Randall Davis <[log in to unmask]>
Reply To:
Randall Davis <[log in to unmask]>
Date:
Mon, 7 Apr 1997 11:56:43 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
     Just a small warning here:  Last week, I learned about quarantine
     files the hard way.  I had a database file which was being reported as
     having an "out-moded root file" by both Query and Adager.  Since the
     database was in a test account which was had nothing of value
     (luckily!), I decided to restore the files in the group (from a known
     good tape, using Orbit's backup/3000).  Imagine my surprise when the
     restore caused a Halt 7 condition (which was repeatable).  HP analyzed
     our dump which told them that there was a Posix link referencing a
     nonexistent permanent file.  The failure occurred in the FOPEN
     intrinsic.  HP identified SR4701342519 to the problem.  As yet, there
     is no patch, nor any plans for one.  FSCHECK did not report any errors
     on the file, directory or extent analysis.  MPEX would not purge the
     files (surprisingly).  I ultimately purged the group, rebuilt the
     group and restored the files satisfactorily.
     Randall Davis
______________________________ Reply Separator _________________________________
Subject: Re: file in quarantine
Author:  Pete Crosby <[log in to unmask]> at Internet_mail
Date:    4/7/97 12:04 PM

[log in to unmask] wrote:

>
>I got the most amazing file system error today;
>
>WARNING!!!DATA READ FROM FILE IN QUARANTINE  (FSWARN 516) : error [516]
>
>This is coming out of Speedware, so I don't have a lot of control, but does
>anyone have any idea what it may be?
>

A file is quarantined on 5.5 when subsystem dump is enabled and a
problem with the structures related to an open file is encountered.
A subsystem dumpfile is created and the file is then quarantined, which
allows only READ access to the file.

FSCHECK has 2 new commands on 5.5:

QPURGE -- will purge file objects in quarantine
QDISPLAY -- will display information regarding file objects in
            quarantine.

Other than reading the data and creating a new file, I don't believe
the original file can ever be made write-accessible again.

All of this is designed to allow a more resilient system and reduce
the number of system aborts, where possible.

--
                            --Pete Crosby
                              [log in to unmask]

ATOM RSS1 RSS2