Conference decwet::advfs_support

1010.0. "What good is verify, issue #2" by NETRIX::"trewitt@pa.dec.com" (Glenn Trewitt) Sat Mar 01 1997 21:59

On another file domain (see the previous note), verify reports several
problems:

Checking tag directories ...
check_tagdir_page: in-use on-disk tag does not have matching in-mem tag hdr
    set tag: 1.32769 (0x00000001.0x00008001)
    tag: 461485.32776 (0x00070aad.0x00008008)
    tag directory page: 451
    tag map entry: 563
    seqNo: 0x8008 (32776)
    vdIndex: 10
    bfMCId (page.cell):  24459.26
check_tagdirs: in-mem tag does not have a matching on-disk tag
    set tag: 1.32769 (0x00000001.0x00008001)
    tag: 461485.32775 (0x00070aad.0x00008007)
Scanning directories and files ...
verify: unable to get info for file
</etc/fdmns/nsl_users_hold/nsl_users_verify_aabbua/trewitt/Mail/inbox/6775.BAK
; [9] Bad file number
verify: unable to get info for file
</etc/fdmns/nsl_users_hold/nsl_users_verify_aabbua/warner/Mail/inbox/133>; [5]
I/O error
Scanning tags ...
Searching for lost files ...
Found possible lost file: ino/tag = 475136
	***  This message repeated for 24,034 files  ***

After I run "verify -f", *none* of these problems have been corrected.

Problem #1: None of the specific errors (other than the "lost files" error)
are corrected.  Am I just supposed to live with this?  Am I sitting on a time
bomb?

Problem #2: The promised symlinks that are generated in lost+found are created
so that they point at the .tags file in a bogus location (relative to the
temporary
mount point).  For example:
   # ls -l /nsl_users/lost+found/file_00483599
   lrwxr-xr-x   1 root     system        62 Mar  1 15:51
/nsl_users/lost+found/file_00483599
     -> /etc/fdmns/nsl_users_hold/nsl_users_verify_aabDza/.tags/483599
These files are completely useless, once the filesystem is mounted.

***  Suggestion #1: make the links relative: ../tags/483599

More disturbing than that, is the fact that these files are merely "possibly"
lost.  When I use tag2name, I sometimes get a working filename:
	cd /nsl_users/.tags
	# /sbin/advfs/tag2name ./483599
	tag2name: msfs_get_name() error
	# /sbin/advfs/tag2name ./483600
	tag2name: msfs_get_name() error
	# /sbin/advfs/tag2name ./483601
	tag2name: msfs_get_name() error
	# /sbin/advfs/tag2name ./483602
	/nsl_users/jefferso/.netscape/cache/18/cache331237D80E30A12.html
So, many of the files in lost+found shouldn't be there at all.

Finally, nothing that I've seen in the manual pages says what to do when I
find out where I'd like to reconnect a particular missing file to.  i.e.
Suppose I discover that .../lost+found/file_00483601 belongs in my home
directory,
what should I do?
	Make a symlink?  I don't think so.
	Copy the file?  What do I then do with the "lost" file?

Help would be appreciated.

Thanks,
	Glenn Trewitt
	Network Systems Laboratory
	Palo Alto, California

[Posted by WWW Notes gateway]