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

[JF Mezei]

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 ?

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".

Then, it finds .log;79 in the [] directory, and complains it isn't
there.  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.

This just in: Backup finally finished !!!!

And the device shows 0 errors.


> Disk $11$DQB0: (CHAIN), device type Maxtor 53073H6, is online, allocated,
>     deallocate on dismount, mounted, software write-locked, file-oriented
>     device, shareable, served to cluster via MSCP Server, error logging is
>     enabled.
> 
>     Error count                    0    Operations completed             423300
>     Owner process           "SYSTEM"    Owner UIC                      [SYSTEM]
>     Owner process ID        20200110    Dev Prot            S:RWPL,O:RWPL,G:R,W
>     Reference count                2    Default buffer size                 512
>     Total blocks            58633344    Sectors per track                    87
>     Total cylinders             7659    Tracks per cylinder                  88
>     Logical Volume Size     58633344    Expansion Size Limit           58662912
>     Allocation class              11
> 
>     Volume label             "MAVIC"    Relative volume number                0
>     Cluster size                   6    Transaction count                     1
>     Free blocks             38037456    Maximum files allowed           4188096
>     Extend quantity               18    Mount count                           1
>     Mount status             Process    Cache name         "_$11$DQA0:XQPCACHE"
>     Extent cache size             64    Maximum blocks in extent cache  3803745
>     File ID cache size            64    Blocks in extent cache                0
>     Quota cache size               0    Maximum buffers in FCP cache       1124
>     Volume owner UIC        [SYSTEM]    Vol Prot    S:RWCD,O:RWCD,G:RWCD,W:RWCD
> 
>   Volume Status:  ODS-5, subject to mount verification, file high-water marking,
>       write-back caching enabled, hard links enabled.


Looks like I have a lot of meat in this with plenty of stuff to
investigate. I'll have to brish off that tool that lets you look at
INDEXF.SYS.

BACKUP/COMPARE is finding errors in specific blocks. But if I type the
file, it appears fine.