[OpenAFS] strange error in directory / volume

[Rubino Geiß]

No, not really. The error persists. Some suggested that logging in two times
(on different workstations) messes up the lock file, because insufficient
(i.e. none at all) support of byte range locking. But in the end is not
reproducible though. We were not able to see this error happen in our test
setup. If it happens to one of our users, we salvage his volume; besides
that we do salvages of all volumes on a regular basis. But be prepared. You
have to salvage the volume three times until the offending file/dir is
removed completely.

Bye, Ruby

> -----Original Message-----
> From: openafs-info-admin@openafs.org 
> [mailto:openafs-info-admin@openafs.org] On Behalf Of Brian J. 
> Smith-Sweeney
> Sent: Monday, April 21, 2003 10:15 PM
> To: Jack Neely
> Cc: openafs-info@openafs.org
> Subject: Re: [OpenAFS] strange error in directory / volume
> 
> 
> Was this problem ever resolved?  I'm experiencing the same 
> behavior with a 1.2.8 server/client as well as the 1.2.8 
> server with a 1.2.9 client.
> 
> It first started happening this weekend when I started using 
> the 1.2.9-rc5 client, but that could just be coincidental.  
> Has anyone figured out a way to actually delete or in any 
> other way deal with this file?  
> 
> -Brian
> On Mon, 2002-12-02 at 07:16, Jack Neely wrote:
> > On Sun, Dec 01, 2002 at 01:05:20PM +0100, Rubino Geiß wrote:
> > > We do have a strange error:
> > > 
> > > ll %gconf-xml-backend.lock/
> > > ls: %gconf-xml-backend.lock/ior: No such file or directory
> > > 
> > > obviously something goes wrong with "ls".  if we use rm -rf to 
> > > delete the whole directory. the error is the same "No 
> such file or 
> > > directory / Cannot delete nonempty dir"
> > 
> > I have this same issue.  Its cropped up for at least three 
> users here,
> > including myself.  We are using Red Hat Linux 7.3/8.0 with 
> OpenAFS 1.2.7.
> > My back end servers are Transarc AFS 3.6 on Solaris.  Looks 
> like some
> > strange bug...
> > 
> > Currently, my only work around is to move the directories 
> containing 
> > the foobar'd GConf lock files so I the user can log in 
> again.  (Then 
> > pray it doesn't happen again.)
> > 
> > Jack Neely
> > 
> > > 
> > > using "bos sal" we encountered the following result. Now you can 
> > > delete the dir; but what has cause the error? How can we avoid it 
> > > happening again?
> > > 
> > > The volume is one of 200 homedirs used by students on 
> rh8.0 / rh7.3 
> > > and some rh7.2 machines. "Genome" is the standard window manager.
> > > 
> > > 
> > > SalvageLog:
> > > @(#) OpenAFS 1.2.7 built  2002-10-27
> > > 12/01/2002 11:53:01 STARTING AFS SALVAGER 2.4 
> (/usr/afs/bin/salvager
> > > /vicepa 536
> > > 871961 -orphans attach)
> > > 12/01/2002 11:53:01 CHECKING CLONED VOLUME 536871963.
> > > 12/01/2002 11:53:01 user.hajnacs.backup (536871963) 
> updated 11/29/2002
> > > 18:26
> > > 12/01/2002 11:53:01 SALVAGING VOLUME 536871961.
> > > 12/01/2002 11:53:01 user.hajnacs (536871961) updated 
> 11/29/2002 18:26
> > > 12/01/2002 11:53:01 dir vnode 15: ./.gconfd/lock/ior 
> (vnode 14): unique
> > > changed 
> > > from 2230 to 2742 
> > > 12/01/2002 11:53:01 dir vnode 15: ./.gconfd/lock/ior 
> (vnode 14, unique
> > > 2230) -- 
> > > parent vnode changed from 23 to 15
> > > 12/01/2002 11:53:01 dir vnode 17: invalid entry:
> > > ./.gconf/%gconf-xml-backend.loc
> > > k/ior (vnode 16, unique 2233)
> > > 12/01/2002 11:53:01 dir vnode 17: 
> ./.gconf/%gconf-xml-backend.lock/ior
> > > (vnode 16
> > > ): unique changed from 2233 to 0 -- deleted
> > > 12/01/2002 11:53:01 dir vnode 23: 
> ./.gnome2/share/cursor-fonts/fonts.dir
> > > already
> > >  claimed by directory vnode 15 (vnode 14, unique 2742) -- deleted
> > > 12/01/2002 11:53:01 Salvaged user.hajnacs (536871961): 
> 1879 files, 14894
> > > blocks
> > > 
> > > --
> > > Rubino Geiss, Universitaet Karlsruhe, IPD Goos
> > > Postfach 6980, D-76128 Karlsruhe, GERMANY
> > > Adenauerring 20a, 50.41 (AVG), Zi. 235 
> > > rubino@ipd.info.uni-karlsruhe.de
> > > Tel: (+49) 721 / 608-8352
> > > Fax: (+49) 721 / 30047
> > > 
> > > _______________________________________________
> > > OpenAFS-info mailing list
> > > OpenAFS-info@openafs.org 
> > > https://lists.openafs.org/mailman/listinfo/openafs-info
> > > 
> -- 
> =
=======================================
> Brian Smith-Sweeney
> Senior Systems Administrator
> University of California, Santa Barbara
> Physics Department
> bsweeney@physics.ucsb.edu
> (805)-893-8366
> =
========================================
> 
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org 
> https://lists.openafs.org/mailman/listinfo/ope> nafs-info
>