[OpenAFS] Help needed: Revovering AFS volume after filesystem crash

Berthold Cogel cogel@rrz.uni-koeln.de
Wed, 23 Jun 2004 15:57:36 +0200


Berthold Cogel wrote:
> Hello!
> 
> After a crash (driver problem) some days ago, we had a problem with a 
> filesystem on a linux file server. Several volumes have been damaged. I 
> was able to recover some of them. But there is one volume that is really 
> troublesome.
> 
> After fsck the complete volume data were located in lost+found. I moved 
> the data back to /vicepag/AFSIDat/l=/lYJ=U/ (VolumeID 537221425) and 
> tried to salvage the volume. What I got in the logs was this:
> 
> SalvageLog:
> @(#) OpenAFS 1.2.8 built  2003-02-11
> 06/21/2004 16:52:28 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager 
> /vicepag 537221425)
> 06/21/2004 16:52:28 No applicable vice inodes on vicepag; not salvaged
> Temporary file /vicepag/salvage.inodes.vicepag.25757 is missing...
> ^@
> 

I solved this one: I got the path wrong. '/vicepag/AFSIDat/l/lYJ=U/' is 
correct. I wrote a tool to get the 'voldirs' from a given VolumeID.
3 Gigs back online now. :-)

> 
> There are two other volumes (empty), whose structure seems to be OK. But 
> the salvager returns errors like this:
> 
> SalvageLog:
> @(#) OpenAFS 1.2.8 built  2003-02-11
> 06/22/2004 15:43:19 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager 
> /vicepae 537221329)
> 06/22/2004 15:43:19 SALVAGING VOLUME 537221329.
> 06/22/2004 15:43:19 Hv.www.p.ceec.117 (537221329) updated 03/24/2004 14:16
> 06/22/2004 15:43:19 Salvaged Hv.www.p.ceec.117 (537221329): 0 files, 0 
> blocks
> ^@

This problem is still open.

Berthold Cogel