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

[Michael Moroney]

JF Mezei <jfmezei.spamnot at vaxination.ca> writes:

>So I decided to do an ana/disk/repair to get the strange error messages
>that don't seem to go away:

>-ANALDISK-I-BAD_FIDNUM, unexpected FID_NUM or FID_NMX field
>-ANALDISK-I-INVHEADER_BUSY, invalid file header marked "busy"
>        in index file bitmap
>%ANALDISK-W-BADHEADER, file (4479,639,0)
>        invalid file header


>Any hints on what this really means ? Interesting that backup only found
>a couple of "invalid structure level files", but ana/disk finds a few
>hundred of the above messages. It does not seem to repair them.

I got several of them as well.  Do you get read errors?  I got them
from corrupted file headers, bad blocks from within INDEXF.SYS

>My hope is that with a reboot (and a volume rebuild that takes 45
>minutes), I'll be able to do a proper backup and then reinitialise the
>disk with a smaller indexf.sys and perhaps it will work fine.

Good luck!  When I saw how slow it was going I figured that maybe a shadow
set copy to a spare drive would be faster.  Mounted the drive as a single
member shadowset, added a spare (SCSI) drive, and wham! The system 
crashed in the shadow driver, first time that this system crashed, ever.
(if power was more stable around here, I'd have uptime of a few years)

Then I tried BACKUP/IMAGE to the spare drive.  Got all the way through to
the end (about a day+) and it failed at the very end, and the resulting
drive won't mount.  The next attempt was a BACKUP/PHYSICAL to the spare
drive, which worked (except for all the errors) although it took nearly 3
days.  I see they changed BACKUP/PHYSICAL to only give a warning if the
dest. drive is not the same size (but is larger) than the source.  I was
ready to hack the UCB to force the copy by making the dest drive the same
size as the source.

I have yet to do an autopsy on the resulting mess to see which files I
lost.  At least I have another copy of most of what I want.
I'll look at that crash dump and see why the shadow driver tossed its
cookies someday, too.