Conference decwet::advfs_support

1029.0. "Can't find file set hdr - tag 4.32769" by NETRIX::"[email protected]" (decatl::johnson) Mon Mar 31 1997 10:06

UNIX 4.0a

I see in note 600, where the only solution is to QAR.  Can you give a 
hint as to how to determine what fileset this is refering to (showfile, 
tag2name, etc): 

on defragment, getting:
		Can't find file set hdr - tag 4.32769

This occurs in a rahter large domain with 5 filesets.  

	showfile -x 
seems to show all the 5 fileset structures.

	showfile -x  4
is a 8k file.

The customer is hoping not to take the filesystems down (in ASE) or run 
fverify.

But if he could determine if it is a fileset issue, could try:
	vdump fileset
	rmfset
	mkfset
	vrestore fileset


We checked tag 4, quota.user, with the sum command and seems ok.
All the filesets known are still mounted and working.


takes ~45minutes to get the error,  no other error info seen or -v{erbose}
messages seen.
=======================< the error he see's on the domain is >===========

# defragment -v upload_domain
defragment: Defragmenting domain 'upload_domain'

Pass 1; Clearing
  Volume 1: area at block 17019904 ( 9619712 blocks): 58% full
defragment: Can't find file set hdr - tag 4.32769
defragment: Can't defragment domain 'upload_domain'




# defragment upload_domain
defragment: Defragmenting domain 'upload_domain'
defragment: Can't find file set hdr - tag 4.32769
defragment: Can't defragment domain 'upload_domain'


[Posted by WWW Notes gateway]

    You should try running showfsets on the domain. You'll get output for
    each fileset in the domain. The Id field will have the tag number in
    it. For example: 2dad7c28.0000dfbb.4.8002 - the 4 is the tag for the
    fileset and 8002 is the sequence number, the rest of the Id is the
    domain Id. showfsets will also print the fileset names, but not the
    mountpoints. You should be able to get the mountpoint from /etc/fstab
    if the fileset was mounted from there.
    
    Hopefully the customer will already have a backup of the fileset. I
    don't know if you'll be able to get one or not due to this error. Let
    us know.

Thanks, found a directory in fileset 4 which seemed hosed,  could not 
access files, but appeared to be there.

customer elected to create a new fileset (dump/restore filesystem).
ahd a error on tag 168361 on the rmfset, but hopefully that got
cleared when the fileset was removed.

"
	here's what I got when I did so:

	# rmfset upload_domain spool_news
	rmfset: remove fileset spool_news? [y/n] y
	delete_tags: bs_access( tag = 168361 ) err = -1038delete_tags: 
		bs_access( tag = 168362 ) err = -1038# 

	It did successfully remove the file set and I've recreated it.  I'm
	about to start running 'defragment' against the domain. 
"
[Posted by WWW Notes gateway]