[OpenAFS] Unable to read inode table, vicepa not salvaged

[Ryan Underwood]

Well, that's interesting.  I ran the salvager again under strace, then
went out to work on my car.  When I came back, the result of a
successful salvage was on my screen.  I didn't change anything, so I
have no idea why the first few tries failed and this one worked.  The
only difference that I know of was running it under strace.

Does anyone know of a good way to prevent the fileserver process being
randomly killed by the OOM killer?

Thanks,

Ryan

On Wed, Mar 16, 2005 at 01:34:20PM -0600, Neulinger, Nathan wrote:
> I know I've seen this before, but I don't remember what caused it.
> 
> Try stracing salvager, and see what file it's looking for just prior to
> the error about the inode table. I have a feeling one file is missing.
> 
> -- Nathan
> 
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  nneul@umr.edu
> University of Missouri - Rolla         Phone: (573) 341-6679
> UMR Information Technology             Fax: (573) 341-4216
>  
> 
> > -----Original Message-----
> > From: openafs-info-admin@openafs.org 
> > [mailto:openafs-info-admin@openafs.org] On Behalf Of Ryan Underwood
> > Sent: Wednesday, March 16, 2005 1:05 PM
> > To: openafs-info@openafs.org
> > Subject: Re: [OpenAFS] Unable to read inode table, vicepa not salvaged
> > 
> > 
> > Is there any way I can be more helpful?  We are 100% down 
> > until I figure
> > out how to fix this.
> > 
> > On Wed, Mar 16, 2005 at 10:43:54AM -0600, Ryan Underwood wrote:
> > > 
> > > Hi,
> > > 
> > > After the Linux kernel stupidly killed the fileserver 
> > process in a OOM
> > > condition, I can't start the fileserver anymore:
> > > 
> > > OpenAFS 1.3.74 built  2004-11-29 
> > > 03/16/2005 03:01:33 STARTING AFS SALVAGER 2.4
> > > (/usr/lib/openafs/salvager)
> > > 03/16/2005 03:01:33 Starting salvage of file system 
> > partition /vicepa
> > > 03/16/2005 03:01:33 SALVAGING FILE SYSTEM PARTITION /vicepa
> > > (device=vicepa)
> > > Unable to read inode table; vicepa not salvaged
> > > 
> > > All of the volumes are marked as needing salvage because 
> > the fileserver
> > > was killed, so I'm not sure what to do next.  There doesn't 
> > seem to be
> > > anything obviously wrong with /vicepa.
> > > 
> > > Aside from the immediate problem, is there any good way to 
> > prevent this
> > > from happening again?  All I can find is a vm_overcommit sysctl
> > > variable.
> > > 
> > > -- 
> > > Ryan Underwood, <nemesis@icequake.net>
> > > _______________________________________________
> > > OpenAFS-info mailing list
> > > OpenAFS-info@openafs.org
> > > https://lists.openafs.org/mailman/listinfo/openafs-info
> > > 
> > 
> > -- 
> > Ryan Underwood, <nemesis@icequake.net>
> > _______________________________________________
> > OpenAFS-info mailing list
> > OpenAFS-info@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-info
> > 
> > 
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
> 

-- 
Ryan Underwood, <nemesis@icequake.net>