[Info-vax] Odd BACKUP error: unsupported file structure !

[AEF]

On Nov 13, 7:03 pm, JF Mezei <jfmezei.spam... at vaxination.ca> wrote:
> The plot thickens...
>
> Backup now shows it is at 100% done but it is still chugging along, and
> it emitted the follwoing:
>
> > %BACKUP-E-OPENIN, error opening $11$DQB0:[WWW_WAP.WEATHER]radar_pickup.log;79 as input
> > -SYSTEM-W-NOSUCHFILE, no such file
> > %BACKUP-E-OPENIN, error opening $11$DQB0:[]radar_pickup.log;79 as input
> > -SYSTEM-W-NOSUCHFILE, no such file
> > %BACKUP-E-OPENIN, error opening $11$DQB0:[]$11$DQB0:[]radar_pickup.log;79°
>
> > DOC$S_WWW.DIRûÿDEVELOPMENT.DIR[ÿ                                          ¸ÿCREATE_DISK5.DIR;ÿ  DECUS.DIR<ÿ
> > -SYSTEM-W-FILESTRUCT, unsupported file structure level
> > %BACKUP-E-OPENIN, error opening $11$DQB0:[]ALPHA_FORT080.ZIP;1 as input
> > -SYSTEM-W-FILESTRUCT, unsupported file structure level
> > %BACKUP-E-OPENIN, error opening $11$DQB0:[]_CACHE_003_.;1 as input
> > -SYSTEM-W-FILESTRUCT, unsupported file structure level
>
> Does Backup/IMAGE traverse the directory structure, or does it simply
> backup all files in INDEXF.SYS ?

Unless something this basic has changed since V6.2:

Both. First a bitmap is made of all the file headers in INDEXF.SYS.
Then BACKUP walks the directory structure, marking each file header in
the bitmap as it goes along. Any remaining files in the bitmap are
backed up under [].

>
> Since this disk is mounted /NOWRITE and system is booted "MIN", the
> radar pickup.log;79 couldn't have been deleted during the days it has
> taken to do this backup.
>
> Notice how initially, it finds the .log;79 in its proper directory, but
> complains about "no such file".

There is a directory entry for it, but there is no file with its
original FID.

>
> Then, it finds .log;79 in the [] directory, and complains it isn't
> there.

This is the leftover in the bitmap, so the file was present during the
initial scan of INDEXF.SYS, which makes the "bitmap".


And finally, it complains that a file with plenty of garbage
> attached after the .log;79 has unsupported file structure (implying it
> has found the file and parsed the header.

Must be from the corruption, or something.

Perhaps the file already wasn't there before you mounted /NOWRITE.

>
> This just in: Backup finally finished !!!!
>
> And the device shows 0 errors.

Ah, but what about "unexpected errors"? Now just exactly what is an
"unexpected error"? Some errors are just expected, I guess. "Gee, I
wasn't expecting an error. I certainly wasn't expecting an unexpected
error! Expected errors, yes. But not unexpected errors."

"But what if you actually expect unexpected errors? Does that cure
them? (~_^).

Pilot: We're expecting some unexpected turbulence on the flight.

[...]
> >     Cluster size                   6    Transaction count                     1

Maybe try a larger cluster size next time.
[...]

AEF