We currently do weekly restarts of our cell. We're not positive it is
still necessary, but we haven't convinced ourselves it isn't either.
Sometimes after a restart one or two volumes (out of 25000 or so)
won't come on-line. More often than not, salvaging will bring the
volume on-line, and the salvage log will look something like this:
> @(#)Base configuration afs3.4 5.28
> 06/01/99 13:25:35 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /vicepd <volume
>id>
> 06/01/99 13:25:50 Scanning inodes on device /dev/rsd9c...
> 06/01/99 13:26:38 CHECKING CLONED VOLUME <cloned volume id>.
> 06/01/99 13:26:38 <volume>.backup (<cloned volume id>) updated 01/13/99 13:49
> 06/01/99 13:26:38 SALVAGING VOLUME <volume id>.
> 06/01/99 13:26:38 <volume> (<volume id>) updated 01/13/99 13:49
> 06/01/99 13:26:38 Volume uniquifier is too low; fixed
> 06/01/99 13:26:38 Salvaged <volume> (<volume id>): 711 files, 7520 blocks
Does anyone know what the "Volume uniquifier is too low; fixed" means.
Or why volumes seem to spontaneously develop this problem? This has
even been known to happen to volumes that get little or no use.
Jonathon Weiss
[EMAIL PROTECTED]
MIT/IS Athena Server Operations
