Here's a new one:
During verify, I will invariably receive between 20 and 150 incorrect link
messages on a clone of a fileset with no errors.
The fileset being cloned is used for a user storage area for the Advanced
Server. The clone is recreated nightly and there is only one fileset in
this domain. Any ideas as to prevent these errors in the future?
Thanks in advance for any ideas/help in the matter.
-Adrian Cole
UNIX Systems Manager
Hood College
The following is a curtailed verify report:
++++++ Fileset nt_clone ++++++
Checking frag file headers ...
Checking frag file type lists ...
Scanning directories and files ...
Scanned 28630 directories.
Scanning tags ...
Scanned a total of 259446 tags.
Searching for lost files ...
verify: bad link count for ino/tag 229388
verify: link count = 1, expected -1073188400
(cut over 200 lines)
verify: bad link count for ino/tag 163489
verify: link count = 1, expected -1073188400
Found 138 files with incorrect link count out of 259584 checked.
Received on Mon Dec 06 1999 - 16:41:32 NZDT