[OpenAFS] Duplicate special inodes in volume header

Hartmut Reuter reuter@rzg.mpg.de
Tue, 20 Nov 2001 15:10:37 +0100


Martin Schulz wrote:
> 
> Hello,
> 
> I just realized that there must be some sincere damage in my AFS...
> there's something wrong with the root.afs.
> 
> When I try to salvage, the SalvageLog says:
> 
> --------------------------------------------------------------------
> @(#) OpenAFS stable 1.0.3 built  2001-04-18
> 11/20/2001 14:25:18 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /vicepa 536870915)
> 11/20/2001 14:25:29 Scanning inodes on device /dev/rdsk/c0t2d0s0...
> 11/20/2001 14:25:49 CHECKING CLONED VOLUME 536870917.
> 11/20/2001 14:25:49 root.afs.backup (536870917) updated 04/20/2001 09:17
> 11/20/2001 14:25:49 CHECKING CLONED VOLUME 536870916.
> 11/20/2001 14:25:49 root.afs.readonly (536870916) updated 10/10/2001 11:08
> 11/20/2001 14:25:49 SALVAGING VOLUME 536870915.
> 11/20/2001 14:25:49 Duplicate special inodes in volume header; salvage of volume 536870915 aborted
> 11/20/2001 14:25:49 Duplicate special inodes in volume header; salvage of volume 536870915 aborted
> 11/20/2001 14:25:49 Volume header salvage was unsuccessful: read-write volume 536870915
> Salvage of volume 536870915 aborted
> ----------------------------------------------------------------------
> 
> The read only copy still works fine (that's why I did not discover it
> any earlier). But I cannot access the RW of those (I actually have
> three of those candidates) volumes, so I cannot rmmount the other
> volumes in them or the like.
> 
> Any hints how to resolve?
> 
> Is there any way to copy the "RO" over the "RW" to get a working RW
> volume again?

You can "copy" the RO to a RW volume by 

vos dump 536870916 0 | vos restore <otherserver> <partition> <name> -id
536870915 -overwrite full


> 
> What are these "special inodes?"

The volume header file contains the volume-id parent-id and the inode
numbers of the volume special files. These files are the "volume Info
file" (length 552), the two vnode files for large and small vnodes and -
if you are using the namei-interface - the "link table". In the case of
the namei-interface this information is redundant because there is an
algorithm to build the pseudo inode-numbers.

The salvager should be able to rebuild the volume-header in the case he
finds all the volume special files. I have no idea how it was possible
to get duplicate special inodes in the header, but - after you have
dumped the RO-volume - you could try to remove the volume-header and
then rerun the salvager.

Hartmut Reuter
> 
> Any hints greatly appreaciated,
> --
> Martin Schulz                             schulz@iwrmm.math.uni-karlsruhe.de
> Uni Karlsruhe, Institut f. wissenschaftliches Rechnen u. math. Modellbildung
> Engesser Str. 6, 76128 Karlsruhe
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info

-- 
-----------------------------------------------------------------
Hartmut Reuter                           e-mail reuter@rzg.mpg.de
					   phone +49-89-3299-1328
RZG (Rechenzentrum Garching)               fax   +49-89-3299-1301 
Computing Center of the Max-Planck-Gesellschaft (MPG) and the
Institut fuer Plasmaphysik (IPP)
-----------------------------------------------------------------