Brett Rickard <[log in to unmask]> wrote:
 
>
>Hp3000 957 Mpe/ix 5.0 powerpatch 3
>
>Here is an interesting/scary one that happened to me.
>
>What happened was a detail data set in an Image database
>"disappeared" between the 1:00am backup  and when the users
>logged on at 9:00am.
>
 
<<some extraneous details deleted. It may be the next line is key>>
 
>4. 9:00 am shutdown and restart the system.(change in printer
>configs).
>
>5. 10 minutes after startup users call about programs aborting.
>
>The database was backed up and so we were able to recover. I
>called the response center and hprc checked my log files for disk
>problems etc. and found no unusual events or errors logged. The
>response center has no similar events recorded.
>
>I still have no idea what happened to that file.
 
Just because the logs do not indicate a disc problem does not
necessarily indicate a media error did not occur. On 5.0 there is a
new functionality which results in a file being made inaccessible if
unrecoverable data was detected during a sparing operation on the way
up. The file gets "locked".
 
Try going into FSCHECK (this is best done on an idle system or a hang
or invalid results could possibly result) and execute the command
"DISPLAYLOCKFILE ALL". This will check for locked files on all mounted
volumes of all volume sets. What you must be aware of, if you find one,
is that the file IS CORRUPT!! This functionality was implemented to
allow users to recover data from the file if necessary, rather than:
 
                 1. pause a reboot and wait for an operator to decide
                    if a file should be purged or saved
 
            or   2. just purge the file, which is inconvenient at best
                     and catastrophic at worst.
 
Unfortunately, due to the volume of console messages during a reboot,
messages about such locked files are missed and then you have something
of a mystery when someone asks where their file went.
 
I hope this helps. I cannot be sure this is what happened to your file
but it is a likely explanation.
 
--
                            --Pete Crosby
                              [log in to unmask]