Original problem was:
>Prior to performing an upgrade from 4.0d to 4.0e I was making sure an advfs
>volume was ok as suggested in the release notes. The system was shutdown
>to single user mode and I ran the 'verify' command on the single advfs
>volume on the machine. It gave the following results:
>
>Scanning directories and files ...
>193200
>Scanning tags ...
>192500
>Searching for lost files ...
>verify: bad link count for ino/tag 83644
>verify: link count = 5, expected 6
>verify: bad link count for ino/tag 19624
>verify: link count = 25, expected 26
>verify: bad link count for ino/tag 20884
>verify: link count = 35, expected 36
>
>I've tried running verify with both the '-f' and '-d' flags to see if it
>would fix these errors (I assume that's what they are) but it
>doesn't seem to make any difference.
Ellen Davis had the same errors during an upgrade. The suggestion
from DEC was to either ignore the error or do a complete dump,
remake the affected filesystem and do a complete restore which would
sort things out.
We decided to ignore the error for now and proceed with the upgrade.
All went well and I'll do the full backup/restore over a weekend at some
stage to get rid of the problem once and for all.
Jim Bostwick has a problem with the root domain which seemed to
have been cured by running verify several times before it did anything!
The filesystem in our case wasn't the root domain but I did try multiple
runs of verify with no luck.
Regards
--
John Kissane
Department of Computer Science, University College Cork, Ireland
Received on Fri Jun 18 1999 - 12:34:20 NZST