Cannot 'vos backup' certain vols, coredumps in AFS, etc (fwd)

[Neulinger, Nathan R.]

I've complained about this before and never gotten squat back from
Transarc/IBM. Their mailserver is a POS... 

-- Nathan

> -----Original Message-----
> From: Jeff Blaine [mailto:jblaine@linus.mitre.org]
> Sent: Tuesday, February 20, 2001 2:54 PM
> To: info-afs@transarc.com
> Subject: Re: Cannot 'vos backup' certain vols, coredumps in AFS, etc
> (fwd)
> 
> 
> Yeah, rock on.  I sent this 5 days ago and just got it from the
> list.  Awesome.
> 
> --On Friday, February 16, 2001 11:19 AM -0500 Jeff Blaine 
> <jblaine@linus.mitre.org> wrote:
> 
> > For hope that someone here might be able to assist me faster than
> > IBM can...
> >
> > Also note that salvager is coredumping as well.  The 
> ramifications of
> > everything below is that 4 .backup volumes are in a completely hosed
> > state and I cannot get rid of them to create new ones.  This means
> > those RWs have not been backed up in several days and I cannot even
> > move the RW volumes off of the server in question:
> >
> > ---------- Forwarded message ----------
> > Date: Fri, 16 Feb 2001 10:47:34 -0500 (EST)
> > From: Jeff Blaine <jblaine@linus.mitre.org>
> > To: afshelp@transarc.ibm.com
> > Subject: Cannot 'vos backup' certain vols, coredumps in AFS, etc
> >
> > We're having some serious problems with several backup volumes on a
> > server of ours.  It would seem that our volserver is coredumping
> > in a reproduceable fashion.
> >
> > - The cell is running AFS 3.6.
> > - The server is running Solaris 2.7 in 32-bit mode.
> > - A 'bos salvage' has ALREADY been done on the volumes 
> below that are
> >   shown as not being able to be attached
> >
> > % vos listvol bunky c
> > ...
> > **** Could not attach volume 536892576 ****
> > **** Could not attach volume 536892561 ****
> > **** Could not attach volume 536892371 ****
> > **** Could not attach volume 536892308 ****
> > % vos examine 536892576
> > **** Could not attach volume 536892576 ****
> >
> >     RWrite: 536892574     Backup: 536892576
> >     number of sites -> 1
> >        server bunky.mitre.org partition /vicepc RW Site
> > % vos remove bunky c 536892576 -verbose -localauth
> >
> > u.tllin
> >     RWrite: 536892574     Backup: 536892576
> >     number of sites -> 1
> >        server bunky.mitre.org partition /vicepc RW Site
> > Transaction on volume 536892576 failed
> > Volume needs to be salvaged
> > Error in vos remove command.
> > Volume needs to be salvaged
> > % vos zap bunky c 536892576 -force -verbose
> > vos: forcibly removing all traces of volume 536892576, 
> please wait...failed with code 1492325127.
> > % bos salvage bunky c 536892574 -localauth
> > Starting salvage.
> > bos: waiting for salvage to complete.
> > bos: waiting for salvage to complete.
> > bos: waiting for salvage to complete.
> > bos: waiting for salvage to complete.
> > bos: waiting for salvage to complete.
> > bos: waiting for salvage to complete.
> > bos: waiting for salvage to complete.
> > bos: salvage completed
> > % vos listvol bunky c
> > ...
> > **** Could not attach volume 536892561 ****
> > **** Could not attach volume 536892371 ****
> > **** Could not attach volume 536892308 ****
> > # NOTE THAT 536892576 is NOT LISTED THIS TIME
> >
> > % vos backup u.tllin -verbose -localauth
> > Creating a new backup clone 536892576 ...Failed to clone 
> the volume 536892574
> > Could not end transaction on the volume 536892574
> > : No such file or directory
> > Error in vos backup command.
> > : No such file or directory
> > % cd /usr/afs/logs
> > % cat VolserLog
> > Fri Feb 16 10:43:27 2001 Starting AFS Volserver 2.0 
> (/usr/afs/bin/volserver)
> > % date
> > Fri Feb 16 10:45:13 EST 2001
> > %
> >
> >
> 
>